Guest networks aren't secure ​

Guest networks are often viewed as a sort of abyss where untrusted traffic finds its home on secure corporate networks. The reason behind this perception is quite straightforward. For decades, the guest network has served as a catch-all for unwelcome traffic and devices, offering internet access to our visitors and a repository for devices we don't inherently trust.

Over time, I've found myself repeatedly engaging in discussions with clients and friends about the security of their guest networks. It's crucial to understand that just because the guest network lacks access to internal services, it shouldn't be regarded as a safe haven for undesirable devices.

One might wonder why there's even a need to connect such devices in the first place. If you find yourself questioning the trustworthiness of a device or hesitate to include it in the same network as your secure devices, the guest network should not be the go-to solution.

Inevitably, there will be occasions, regardless of your security practices, when a secure device ends up connected to the guest network. If you've been neglecting the security of your guest network, this could spell disaster.

Therefore, it's imperative to redefine the guest network for what it truly is: a guest network. Its primary purpose is to provide temporary internet access for visitors, with no access to internal services. Devices that don't belong on the secure network but aren't guests should find a different home.

IoT devices, for instance, should have their own dedicated network with a unique set of security policies. So, let's change our perspective and stop considering the guest network as a dumping ground for undesirable traffic.

Stop thinking about the guest network as a dumping ground for undesirable traffic