in this guide
Every office has a password that is not on any access list. It is on a card at reception, on the meeting-room whiteboard, in the onboarding email, and saved on the phone and laptop of every employee, contractor, candidate and courier who ever asked for it. It is the Wi-Fi password, and it lets whoever holds it onto the same network as the printer, the file server and the people at their desks.
Offboarding does not touch it. The leaver’s email is switched off and their laptop comes back, but their personal phone still remembers the office network, and so may the phone of a contractor who left years ago. Nobody changes the password because changing it means walking round every printer, camera and meeting-room screen.
This guide is about that key: who holds it, what it opens, and how to get to a network where access belongs to a person. It pairs with the guide on boxes at the network edge, which covers the admin logins of the router and the Wi-Fi controller themselves. One note on words: guest Wi-Fi is a different thing from the guest user accounts in Microsoft 365 and Google, which have their own guide.
how one wi-fi password travels
- 1set onceThe provider or an early employee picks it on install day.
- 2handed outReception card, onboarding email, phone-to-phone sharing.
- 3never changedChanging it would knock every printer and screen offline.
- 4still savedOn the devices of people who left years ago.
The Wi-Fi password is a login with no name on it and no end date.
one key, every person, no names
An office network with one password runs in what the standards call Personal mode: WPA2-Personal or WPA3-Personal, one passphrase for the whole network. Picture a 90-person firm on that setup. Staff, visitors’ laptops, the CEO’s tablet and the smart TV in the boardroom all use the same passphrase. The network sees devices. It has no idea which person is behind each one, and it has no way to remove one person except by changing the key for everyone.
The key also travels on its own, by design.
Phones pass it on. Apple’s support documentation describes how an iPhone or iPad connected to a network can share its password with a nearby device of someone in its contacts: the other person taps the network name and the owner taps Share Password. Google’s Android help describes a Share button on a saved network that produces a QR code another device can scan to join. Neither step goes through the person who manages the network.
Copies outlive the job. A saved network stays on a personal phone after its owner leaves the company. The leaver checklist on this site already lists Wi-Fi among the shared logins to change when someone goes. In a shared-key setup, that step means a new password for everyone.
One login for many people erases the record. The same problem in admin consoles is covered in the topic on shared admin accounts: when everyone uses the same credential, nobody can say who used it.
what the key opens
Holding the Wi-Fi password puts a device on the inside of the network, within radio range of the building. That range does not stop at the office door. A car park, a corridor or the floor above can be close enough.
On the network, the device sits next to everything else. In a small office the Wi-Fi and the wired network can be one flat network: laptops, printers, the storage box, cameras and sometimes the till or the door controller all reachable from any connected device. The Target incident shows what a network that was not walled off meant at scale.
With WPA2-Personal, the key can also read other people’s traffic. The Wireshark project’s documentation explains that decrypting WPA or WPA2-Personal traffic needs two things: the passphrase and a captured four-part handshake from the device being watched. Anyone who knows the office password has the first. The same page says WPA3 uses a different key for each connection, so the passphrase and handshake are no longer enough. Traffic protected by HTTPS keeps that protection. Anything the office still sends in the clear can be read.
WPA3-Personal helps with guessing, and leaves the sharing problem. Cisco’s WPA3 deployment guide says WPA3-Personal resists offline dictionary attacks by limiting password guesses and provides forward secrecy. The Wi-Fi Alliance describes it as giving increased protection from password guessing. Both are improvements. With WPA3-Personal there is still one key, held by everyone who ever had it, and the same guide warns that a mixed WPA2 and WPA3 “transition” setup lets attackers force devices down to WPA2.
the case on the record
Wireless entry has a long paper trail. In March 2008 the US Federal Trade Commission announced a settlement with the retailer TJX. The FTC alleged that TJX did not use readily available measures to limit wireless access to its networks, which let an intruder connect without authorization and eventually obtain tens of millions of payment cards. Those were the FTC’s allegations, resolved by settlement.
A recent case shows what a Wi-Fi password is worth to an attacker, even on a network where each person signs in with their own. On 22 November 2024 the security firm Volexity published research on what it calls a “Nearest Neighbor Attack”, investigated from February 2022.
The attacker got passwords from outside. According to Volexity, a password-spray attack against an internet-facing service of the victim, which Volexity calls Organization A, compromised three accounts. That service required MFA, so the passwords alone did not open it.
The Wi-Fi asked for less. Volexity writes that the enterprise Wi-Fi network “did not require MFA” and only needed a valid domain username and password.
The attacker was never near the building. Volexity reports that the intruder compromised other organisations in nearby buildings, found machines there with both a wired connection and a Wi-Fi card, and used them to join Organization A’s Wi-Fi from nearby.
The guest network was the way back. When the attacker returned later, Volexity says the entry point was a system reachable from both the guest Wi-Fi and the wired corporate network, although the guest network had been believed to be completely isolated.
Volexity assesses with high confidence that the actor is the group it tracks as GruesomeLarch, also known as APT28. That attribution is Volexity’s own assessment. Its recommendations include separate network environments for Wi-Fi and wired networks, harder access requirements for Wi-Fi such as MFA or certificates, and treating Wi-Fi access with the same care as a VPN.
the guest network that reaches the printer
A guest network exists so visitors do not need the staff password. It only does that job if it is cut off from everything else, and that is a setting someone chooses.
TP-Link’s user guide for its Archer AX10 router shows how plain the choice looks. Under guest permissions there are two checkboxes: one lets guest devices see each other, and the other lets guests access the local network, meaning the devices on the router’s main network and LAN ports. Ticking the second box is one way to let a visitor print. It also puts every visitor’s device on the same network as the staff’s.
The same goes for devices nobody thinks of as people. The FTC’s guidance on security cameras, published in February 2023, suggests putting cameras on a separate network from computers and printers, so that someone who gets into a computer or the main network cannot easily reach the cameras. Printers, cameras and smart screens are the reason the main key never changes, and they belong on a network of their own.
the ways onto one office network
- staff Wi-Fi passwordshared, saved on leavers' phones
- guest Wi-Fiwith "access local network" ticked
- router admin logindefault or set by the provider
- meeting-room network portlive, on the main network
- per-person Wi-Fi loginremoved with the person
- isolated guest networkinternet only
outside any reviewtied to a person or cut off
the router’s own login
Behind the Wi-Fi password sits a second shared credential: the admin login of the router or access point, which sets the Wi-Fi password, the guest permissions and remote management. CISA’s advice on wireless networks, released in February 2021, starts with changing default passwords, and in December 2023 CISA published a Secure by Design alert asking manufacturers to stop shipping static default passwords altogether.
In a small office, that login can sit with whoever installed the router, which may be the IT provider. The edge devices guide covers what to do with it: name an owner, check whether the admin page answers from the internet, and know who receives the vendor’s security notices. For this guide the point is simpler. Whoever holds the router login can change the Wi-Fi password, and can also read it.
from one key to a key per person
There are three practical steps up from a single shared key. They can be taken one at a time.
shared key and per-person access, side by side
one shared key
WPA2 or WPA3-Personal
- Everyone who ever joined can join again
- Removing one person means a new key for all
- No record of which person connected
a key or login per person
per-device keys or WPA3-Enterprise
- Each person or device has its own credential
- One credential is removed, the rest keep working
- Connections point to a name
Split the networks and rotate the shared key. Put visitors on an isolated guest network with its own password, changed on a schedule, and put printers, cameras and screens on a separate network for devices. The staff network then has fewer things on it that break when its key changes, so changing it when someone leaves becomes possible.
Give each person or device its own key. Some business Wi-Fi products let one network accept many passphrases. Cisco Meraki’s documentation is one documented example: its identity PSK feature allows up to 5,000 keys per wireless network (SSID) on firmware MR 30.1 and newer, each tied to a group policy, and removing one key disconnects only the devices that used it. The same documentation says the feature does not support WPA3. Other vendors offer similar features under other names; check your own equipment’s documentation. Naming one here is an example, and no endorsement.
Move staff to named logins. WPA2 or WPA3-Enterprise uses 802.1X, where each user or device signs in with its own credential checked by a RADIUS server, which Cisco’s WPA3 guide describes. Volexity’s recommendations name certificates and MFA as ways to harden Wi-Fi sign-in. With certificates on company-managed devices, the step its case turned on goes away: a stolen password alone no longer joins the network. This step needs a RADIUS service and device management, so it is the one to ask a provider to scope.
When the new staff password goes out, how many devices will stop working, and whose are they?
sources
- Volexity: The Nearest Neighbor Attack: How A Russian APT Weaponized Nearby Wi-Fi Networks for Covert Access, 22 November 2024 (vendor research)
- Wireshark wiki: How to decrypt 802.11
- Cisco: WPA3 Deployment Guide (updated 6 October 2025)
- Wi-Fi Alliance: Security
- CISA: Securing Wireless Networks (released 1 February 2021, archived)
- CISA: Secure by Design Alert: How Manufacturers Can Protect Customers by Eliminating Default Passwords, 15 December 2023
- TP-Link: Archer AX10 and AX1500 user guide, chapter 6: guest network
- Apple Support: How to share your Wi-Fi password from your iPhone or iPad (published 17 March 2026)
- Google: Connect to Wi-Fi networks on your Android device
- Cisco Meraki: IPSK Authentication without RADIUS
- Cisco Meraki: IPSK with RADIUS Authentication
- FTC: How to secure your home security cameras (February 2023)
- FTC: Agency announces settlement of separate actions against retailer TJX, and data brokers Reed Elsevier and Seisint, 27 March 2008
