Use conference Wi-Fi for low risk tasks such as browsing schedules, reading docs and watching talks. Switch to your phone hotspot for anything that signs in to work systems, and avoid deploys, secret handling and first time logins on the venue network. Treat it like any shared network, only with more people.
What makes conference networks different
A conference gathers a large number of devices, many of them belonging to security minded people, in one place. The network is run for the event, often by a contractor, with a name you may only know from a slide. Several of the usual risks line up: shared segment, unknown operator, a crowd of devices, and lots of fake network names that look plausible.
For general background, read Is public Wi-Fi safe? Myths and facts. For the full travel list, see Conference travel security checklist.
Decision table
| Task | Venue Wi-Fi | Phone hotspot |
|---|---|---|
| Read schedule, docs, social media | Fine | Fine |
| Join a talk stream | Fine | Fine, mind data use |
| Sign in to email or chat | Acceptable with MFA | Better |
| Open a pull request | Acceptable with HTTPS | Better |
| Cloud console, production tools | Avoid | Use this |
| First sign in to a new service | Avoid | Use this |
| Handling secrets or key rotation | Avoid | Use this or wait |
Rules that hold up
- Confirm the network name with organisers, from a sign, not from a list. An evil twin can copy a name, as in What is an evil twin Wi-Fi network?.
- Stop at certificate warnings. HSTS removes the bypass option for sites it covers, which makes the warning meaningful. See Does HTTPS protect you on public Wi-Fi?.
- Do not install certificates, profiles or helper apps offered on a sign in page.
- Turn off auto join, file sharing and Bluetooth discovery while on the floor.
- Use MFA that resists phishing for work accounts.
- Leave the laptop firewall on and do not run local servers open to the network.
Demo day and workshop tips
If you are presenting, bring the demo offline or record a video. Do not rely on venue Wi-Fi for a live demo, and do not show secrets on screen. If a workshop asks you to join a lab network or install a script, run it in a disposable virtual machine or container, not on your main laptop.
On return
Forget the conference network, update your devices and review sessions. The post trip checklist covers it.
For organisers
Publish the network name in several places, use a distinct name, and consider Enhanced Open for the guest network, as covered in What is WPA3 Enhanced Open?.
Safeguard does not secure venue networks. It does dependency scanning, SBOMs and policy gates, so a hallway commit gets the same checks as one from the office. A free scan shows your repository baseline.
Quick check
Is conference Wi-Fi more dangerous than hotel Wi-Fi?
It is a similar kind of risk with more devices and more incentive for attackers. The same rules apply, applied more strictly.
Can I push code from the venue network?
Over HTTPS or SSH with valid host checks, yes, with the usual care. For production deploys, use a hotspot or wait.
Sources
Last reviewed: 19 October 2026.
