Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Wireless penetration testing assesses the Wi-Fi networks around a site: how they authenticate, how they are segregated, and whether an attacker in the car park can get onto them.

What Is Wireless Penetration Testing?
A wireless network puts your corporate perimeter in the street outside. Wireless penetration testing measures what that actually means for a given site: which networks are broadcasting, how strong their authentication is, what a connected device can reach, and whether an attacker sitting in a car park or an adjacent office can get in or persuade your staff to connect to them instead.
It is a physical as well as a technical exercise. The tester has to be within radio range, which is why this work is usually scheduled as an on-site visit and often combined with physical penetration testing.
| Target | Weakness |
|---|---|
| WPA2 with a pre-shared key | The handshake can be captured and the passphrase attacked offline; the PMKID method removes the need to wait for a client to connect |
| WPS | Weak implementations allow the PIN to be recovered, yielding the passphrase regardless of its strength |
| WPA2-Enterprise | Clients that do not validate the server certificate can be lured to a rogue authentication server that captures credential material |
| Open guest networks | No encryption between client and access point; captive portals are frequently bypassable |
| Management frames | Without protected management frames, deauthentication can be forged to disconnect clients at will |
| WPA3 | Stronger by design, but the Dragonblood research published in April 2019 showed downgrade and side-channel weaknesses in early implementations, and transition mode reintroduces WPA2 exposure |
Two named pieces of research shaped current practice. KRACK, disclosed in October 2017, attacked the WPA2 four-way handshake itself through key reinstallation and was fixed by patching clients and access points. Dragonblood, in 2019, targeted the WPA3 handshake. Both are reminders that firmware currency matters on access points and on the devices that connect to them.
The most productive finding in many engagements has nothing to do with cracking. A tester broadcasts a network name that staff devices remember, those devices connect automatically, and the tester is now between the user and everything they do. This is the evil twin attack, and it works because operating systems were designed to reconnect to known networks without asking.
The enterprise variant is sharper. If a laptop is configured to authenticate to a corporate network without validating the server certificate, it will happily authenticate to a fake one, handing over material that can be cracked offline. One misconfigured group policy can expose every domain credential in the building.
Testing begins with a survey: every network in range, its channel, encryption, signal strength, and physical reach, which is usually mapped so the client can see how far their coverage extends beyond the building. Connected clients are enumerated, including devices that are advertising the names of networks they remember.
Attacks then follow the agreed scope. Handshake capture and offline cracking against the corporate pre-shared key, enterprise authentication testing with a rogue server, and controlled rogue access point tests against staff devices are the common three. Where a tester gets onto a network, the next question is segregation: can a guest network reach internal resources, can a device on the staff wireless reach the server VLAN, is there any authentication beyond the wireless layer.
Scope discipline is essential, because radio does not respect property boundaries. The rules of engagement must name the networks in scope by identifier, exclude neighbouring organisations explicitly, and set limits on deauthentication, which disrupts service. In the UK, interfering with other people’s wireless communications engages the Wireless Telegraphy Act 2006 as well as the Computer Misuse Act 1990.
Our Network Security Services include wireless assessment alongside wired infrastructure testing, because an attacker who gets onto the wireless network will immediately start looking for the next segment.
No. WPA3 fixes the offline dictionary attack against captured handshakes, which is a significant improvement, but research has shown weaknesses in early implementations and transition mode keeps WPA2 available for older clients. Testing also covers segregation, rogue access points, client configuration, and what a connected device can reach, none of which WPA3 addresses.
Further than most people assume. A standard laptop adapter works across a car park, and a directional antenna extends that to hundreds of metres with line of sight. Part of the value of a survey is mapping where your coverage actually reaches, which often includes neighbouring buildings and public areas that nobody considered when the access points were sited.
It is if it touches anything internal. A guest network should provide internet access and nothing else, with client isolation enabled so devices cannot see each other, and no route to corporate resources. The common failure is a guest network sharing a VLAN, a management interface, or a printer with the staff network.
Only partially. Configuration review of access points and controllers can be done remotely, and it finds plenty. Radio-layer testing requires physical presence, since capturing handshakes, running a rogue access point, and measuring signal reach all depend on being within range. Most engagements combine a remote configuration review with an on-site visit.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.