|
Given they have picked a few platforms, but are leaving a lot of choices up to the individual organizers, presenters, etc — aside from having: — burner hardware,
— one-time network connections,
— one-time user accounts,
— one-time identifiers,
— read-only OS builds,
— physically disabling sensors,
— (insert suggestions) What else might be options for securely accessing the event? |
I generally recommend ensuring that your security posture for DEFCON is the same baseline security posture you should have at all times, and for all websites, and then adjusting your habits accordingly months in advance... and then just chilling out because you've adopted a more secure normal (and DEFCON isn't particularly risky compared to everyday life).
Pantomiming paranoid-level security during hacker summer camp is silly. This is true for both in-person events and this year's virtual event.
If you're worried about getting hacked at DEFCON, don't wait until DEFCON to become secure, and don't become lax after DEFCON is over.