Let us set up wireless for a small invented company, a 60-person design studio in Pune, and make each security decision in turn. The point is not a recipe but understanding why each choice is made, because the wrong folk advice about Wi-Fi is very widespread.
Step 1: the name of the network
Someone suggests hiding the SSID (the network name) so outsiders cannot see it. This achieves very little. The name still appears in management frames whenever a device connects, and freely available tools reveal it in seconds. Hiding it can even make laptops probe for the network by name wherever they go, which leaks information. Skip it. Choose a plain name and, if you like, avoid putting the company name in it for tidiness rather than security.
Step 2: restricting by device address
Next idea: allow only listed MAC addresses. A MAC address is a hardware identifier sent in the clear on every frame, so someone observing the network can see which addresses are allowed and copy one. Many devices now also randomise their MAC for privacy, which makes filtering clumsy. MAC filtering costs administrative effort and gives no real protection against a determined person. Real device control comes from authentication, below.
Step 3: encryption and the protocol generation
Wireless traffic travels through the air, so it needs encryption. Open networks have none. The old WEP scheme can be broken within minutes and must not be used. WPA2, using AES-based CCMP encryption, has been the standard for years and remains acceptable when configured properly. Its personal (shared password) mode has a known weakness: an attacker who captures the connection handshake can try passwords offline, guessing as fast as their hardware allows. A weak passphrase will fall.
WPA3 improves this. In personal mode it replaces the key exchange with one called SAE, which makes offline guessing against a captured handshake impractical, and it gives forward secrecy, meaning recording traffic today and learning the password tomorrow does not reveal past sessions. It also requires protected management frames, which blocks some forced-disconnection tricks. Where all devices support it, use WPA3; many networks run a transition mode that accepts both, which is a sensible compromise while older gadgets remain. Avoid the WPS push-button or PIN feature, which has well-known weaknesses.
Step 4: one shared password is the real problem
With a shared passphrase, every employee knows it, so when someone leaves you must change it on every device. Contractors share it with friends. A lost laptop holds it. For a 60-person company, move to enterprise mode (WPA2-Enterprise or WPA3-Enterprise), also called 802.1X. Each person authenticates with their own identity, usually through a RADIUS server linked to the company directory, using either a username and password protected inside a tunnel or, better, a device certificate. When someone leaves, you disable one account.
Pay attention to client configuration. If laptops are not told which server certificate to trust, they may connect to a rogue access point that imitates the network, an “evil twin”, and hand over credentials. Push a profile that pins the correct RADIUS certificate to every device.
Step 5: separate networks for separate trust
Visitors, personal phones, printers, smart TVs and staff laptops should not share one flat network. Create a guest network with internet access only and client isolation, so one guest device cannot reach another. Put corporate devices on their own segment with access to internal resources. Give IoT devices, which are often weakly secured, their own restricted segment. If a guest’s phone is infected, it then meets a closed door.
Step 6: keep watching
Update access point firmware, change default admin credentials and manage controllers from a restricted network. Many wireless platforms offer rogue access point detection, which flags unknown devices broadcasting your network name or plugged into your wired network. Log authentication events and send them to your SIEM; repeated failures or logins from impossible combinations deserve a look.
Wi-Fi security protects the radio link only. Once traffic leaves the access point it is as exposed as any other, so HTTPS and a VPN where appropriate still matter. And at a cafe or airport, the same lesson applies from the user’s side: prefer your phone’s hotspot over an unknown open network for anything sensitive.
The company in the example is illustrative.
Leave a Reply