Wireless Security Testing

Wireless Penetration Testing

Comprehensive security assessment of wireless networks, including WiFi, Bluetooth, and IoT communications. Identify vulnerabilities before attackers exploit your wireless infrastructure.
A penetration tester working at a laptop with a network map on a second screen
Senior
Testers
Quoted
After Scoping
Scoped
Rules of Engagement
Remediation
Reports Included

Wireless Attack Vectors

Comprehensive testing across all wireless communication protocols

WiFi Network Security

Comprehensive assessment of wireless network infrastructure

WPA/WPA2 Cracking
Evil Twin Attacks
Deauthentication
Rogue Access Points

Bluetooth Security

Test Bluetooth implementations and device security

Bluejacking
Bluesnarfing
Device Discovery
Protocol Exploitation

Enterprise WiFi

Advanced testing of enterprise wireless solutions

802.1X Bypass
Certificate Attacks
RADIUS Exploitation
EAP Vulnerabilities

IoT Wireless

Security assessment of IoT and smart device communications

Zigbee Attacks
LoRaWAN Testing
RF Signal Analysis
Protocol Fuzzing

Scope of testing

What a wireless test covers

A wireless penetration test answers one question: can someone within radio range, without your permission, reach something they should not? These are the areas we test to answer it. Pick one to see what we look at, what we often find and the usual fix.

Networks protected by one shared password. Simple to run, but the password is the whole defence, and everyone who has ever joined knows it.

What we test

  • Capture of a connection handshake, then offline cracking against wordlists built for your organization
  • Whether WPA3 networks run in transition mode, letting older devices fall back to WPA2
  • Protected management frames (802.11w), which stop attackers knocking clients off to capture a reconnect
  • Where the shared password is written down, printed or stored in plain sight

What we often find

  • A password based on the company name and a year, cracked in minutes
  • The same password on corporate and guest networks
  • A key that has not changed since staff who left were given it

The usual fix

Move staff devices to 802.1X. Where a shared key must stay (for example, for devices that cannot do anything else), use a long random key per device group, rotate it, and keep that network away from anything sensitive.

Enterprise Wi-Fi authenticates each user or device against your directory through RADIUS. It is the right design, but small client settings decide whether it holds up.

What we test

  • Whether clients check the RADIUS server certificate and the server name before sending credentials
  • Which EAP methods the network accepts: PEAP with MSCHAPv2, EAP-TTLS, EAP-TLS
  • Captured challenge and response pairs and how quickly they crack
  • Fallback networks, guest bypasses and machine accounts with more access than needed

What we often find

  • Laptops set to “do not validate server certificate”, which hand a password hash to any access point using the right name
  • Phones joined by staff themselves, with no profile and no certificate pinning
  • A legacy PSK network kept for one old device that bypasses 802.1X for everyone

The usual fix

Push the wireless profile through device management with server certificate validation and the exact server name enforced. Move to EAP-TLS with device certificates where you can, so there is no password to steal.

An access point you did not install. Either plugged into your network (a rogue) or broadcasting your network name from the car park (an evil twin).

What we test

  • A sweep of every transmitter in range, compared with your list of approved access points
  • Tracing unknown access points to switch ports where possible
  • Standing up a lookalike of your corporate and guest networks to see which devices join
  • Whether your wireless intrusion detection notices, and whether anyone is alerted

What we often find

  • A consumer router a team plugged in to fix poor coverage in one room
  • Hotspots on staff phones bridging to the corporate network
  • Intrusion detection that logs the evil twin but sends the alert nowhere

The usual fix

Enable rogue detection on your controller and send its alerts to someone who acts on them. Use network access control or port security on wired ports, and make certificate validation mandatory so evil twins get nothing useful.

Guest Wi-Fi exists so outsiders never touch your network. We test whether that is actually true.

What we test

  • From the guest network: reaching internal ranges, printers, cameras, controllers and management interfaces
  • Client isolation: whether guests can reach each other
  • Captive portal bypasses and vouchers that never expire
  • Firewall rules between the guest VLAN and everything else, not just the VLAN itself

What we often find

  • A guest network on its own VLAN but routed to the internal network by an allow-any rule
  • The wireless controller’s admin page reachable from the guest side
  • Patients or customers able to see each other’s devices

The usual fix

Enforce isolation at the firewall with a default deny from guest to internal, turn on client isolation, and send guest traffic straight to the internet. Test it again after every network change.

Most wireless attacks target the laptop or phone, not the access point. Devices give away a lot before they ever connect.

What we test

  • Probe requests: which network names your devices broadcast while looking for known networks
  • Whether devices auto-join open or lookalike networks with a remembered name
  • What an attacker could capture once a device joins a hostile network
  • Wireless profiles pushed by device management compared with what is actually on devices

What we often find

  • Laptops broadcasting the name of the corporate network and the CEO’s home network
  • Devices that join any open network called the same as a hotel or airport they once used
  • Personal devices with corporate email joined to corporate Wi-Fi without management

The usual fix

Manage wireless profiles centrally, remove auto-join for open networks, and require a VPN or always-on secure tunnel when devices are off your network.

Cameras, badge readers, medical devices, handheld scanners and plant radios. They often cannot do 802.1X and are rarely patched, so separation matters more than for laptops.

What we test

  • Which network each device class uses and what it can reach from there
  • MAC address filtering, which is easy to copy and is not authentication
  • Default credentials on wireless devices and their management interfaces
  • Industrial radios and wireless bridges to the plant floor, observed passively first

What we often find

  • Cameras and staff laptops on the same network
  • A wireless bridge into the control network with the default password
  • Scanners sharing a key that has been printed on a label for years

The usual fix

Give each device class its own network and firewall zone, allow only the traffic each one needs, and keep OT wireless separate from corporate. For plants and utilities this often sits alongside our OT security work.

More on OT and ICS security

Personal or Enterprise

How the main Wi-Fi security modes compare

Most findings come down to which mode a network uses and how its clients are configured. This is how each one works, how it is usually attacked and when it is the right choice.
Comparison of WPA2-Personal, WPA3-Personal, 802.1X with PEAP and 802.1X with EAP-TLS
AspectWPA2-PersonalWPA3-Personal802.1X with PEAP802.1X with EAP-TLS
How devices joinOne shared password for everyoneOne shared password, using the SAE handshakeEach user’s directory username and password, checked by RADIUSA certificate on each device, checked by RADIUS
Typical attackCapture a handshake, crack the password offlineForce a fallback to WPA2 when transition mode is onEvil twin collects password hashes from clients that skip certificate checksVery little at the wireless layer; attackers target certificate issuance instead
When someone leavesChange the password on every deviceChange the password on every deviceDisable their accountRevoke the device certificate
Good fitSmall sites and devices that support nothing else, on an isolated networkThe same, where all devices support WPA3Staff devices, as a step towards certificatesManaged staff laptops and phones

Open networks with a captive portal are common for guests. They encrypt nothing, so the question is only ever what they can reach.

On site

How an engagement runs, and what you arrange

Wireless testing has to happen within radio range, so most of the work is on site. Planning the visit well is what keeps it to the days quoted.
  1. Two weeks beforeYou and us

    Scoping and authorization

    We agree sites, floors, networks in scope, testing windows and stop conditions, and collect written authorization. You send the list of approved access points and network names.
  2. Day one, morningGuardsArm

    Walk-through survey

    We walk the site, inside and out, recording every network, access point and transmitter in range, and signal strength at the edges, including the car park and shared corridors.
  3. Day one onwardsGuardsArm

    Active testing

    Handshake capture and password strength, 802.1X and certificate validation, evil twin tests, guest isolation and rogue tracing. Anything disruptive, such as deauthentication, only in agreed windows.
  4. Last day on siteYou and us

    Same-day debrief

    A short walk-through with your contact before we leave. Anything critical, such as guest access to internal systems, is reported the moment we confirm it, not at the end.
  5. Within two weeksGuardsArm

    Report and remediation call

    Findings with evidence, risk ratings and configuration-level fixes, plus a heat map of coverage beyond your walls. We walk your network team through it.
  6. After you fixGuardsArm

    Retest

    We retest the findings you have fixed, often remotely for configuration changes, and confirm the result in writing for your auditor or insurer.

What we ask you to arrange

Most delays on site come from a locked floor or a missing contact. Sort these before day one:

  • Access to every area in scope, with escorts where needed, and a heads-up to building security and reception
  • One contact on site who can answer questions and reach the network team
  • A list of approved access points (controller export is ideal) and the network names you expect
  • A standard staff laptop or test account, and a guest voucher if your portal uses them
  • Agreed windows for anything that might briefly disconnect users
  • Written authorization from the organization, and from the landlord if networks are shared

Testing is non-destructive by default. Techniques that can briefly disconnect a client are only used inside windows you approve, and never against medical or plant floor devices without your operations team.

Interactive tool

Scope your wireless test

Six questions about your sites and networks. You get the test modules we would recommend and why, what you would need to arrange, an indicative effort and a summary to paste into a quote request.

1. Six questions about your wireless

Skip anything you do not know. We fill it with a typical answer and tell you which ones.

How many sites have Wi-Fi?

Offices, clinics, branches, stores, warehouses or plants.

What is the largest site like?

Size and construction drive how long the walk-through survey takes.

How do staff devices join corporate Wi-Fi?

Check the network settings on a work laptop if you are not sure.

Is there a guest network?

For visitors, patients, customers or contractors.

Which other wireless devices do you rely on?

Anything on Wi-Fi or another radio that is not a laptop or phone.

Why are you testing?

This shapes the report, not the testing itself.

After the report

Remediation patterns that hold up

Wireless findings repeat across organizations, and so do the fixes. These are the changes we most often recommend, roughly in order of impact.

EAP-TLS with device certificates removes the password from wireless authentication entirely, so evil twins and handshake cracking have nothing to take. If you stay on PEAP for now, enforce server certificate validation and the exact server name in a managed profile: that single setting closes the most common enterprise Wi-Fi finding.

Default deny from guest to everything internal, enforced on the firewall rather than relying on VLANs alone, with client isolation on. Then add a recurring check, because guest isolation is the setting most often broken by later network changes.

For devices that only support a pre-shared key, use per-device or per-group keys if your platform supports them, make them long and random, rotate them when people leave, and give those devices their own network and firewall zone.

Require 802.11w where clients support it, disable WPA/TKIP and WEP outright, and plan the end of WPA3 transition mode once older devices are replaced.

Most controllers detect rogue and lookalike access points. Few organizations route those alerts anywhere. Send them to your SOC or ticketing system, and pair them with port security or network access control on wired ports so a plugged-in rogue cannot bridge in.

Cameras, building systems, medical devices and plant radios each get their own network with only the flows they need. MAC filtering can stay as a convenience, but it is not a control. For OT, keep wireless off control networks unless there is a documented, monitored path.

Wireless is one way in. To see what an attacker could reach once connected, pair it with internal penetration testing.

Why Choose Our Wireless Testing

Protect your organization from wireless-specific threats and ensure compliance

Prevent Unauthorized Access

Identify and remediate wireless vulnerabilities before attackers exploit them to gain network access.

Protect Sensitive Data

Ensure wireless communications are properly encrypted and cannot be intercepted or decrypted.

Meet Compliance Requirements

Satisfy regulatory requirements for PCI DSS, HIPAA, and other frameworks requiring wireless security testing.

Detect Rogue Devices

Discover unauthorized access points and devices connected to your wireless infrastructure.

Real-World Attack Simulation

Realistic attack scenarios run by senior practitioners on our team, within agreed rules of engagement.

Comprehensive Reporting

Receive detailed findings with risk ratings, evidence, and step-by-step remediation guidance.

Professional Testing Tools

Established wireless assessment tools, alongside manual testing

Aircrack-ng
WiFi security assessment suite
Wireshark
Network protocol analyzer
Kismet
Wireless network detector and IDS
Reaver
WPS attack tool
Wifite
Automated wireless auditing
Bettercap
Network attack and monitoring framework
Hashcat
Password recovery tool
BlueHydra
Bluetooth device discovery

Wireless Testing Packages

Choose the package that fits your wireless security needs

Basic Wireless Assessment

On consultation

3-5 days

  • WiFi network security testing
  • Smaller sites with a single wireless network
  • WPA/WPA2 encryption analysis
  • Rogue AP detection
  • Basic security report
  • Remediation guidance
Request a risk review about the Basic Wireless Assessment
Recommended

Comprehensive Wireless Test

On consultation

5-7 days

  • Full WiFi infrastructure testing
  • Multiple networks, including guest and staff
  • WPA3/Enterprise security testing
  • Bluetooth security assessment
  • Client device testing
  • Detailed technical report
  • Executive summary
  • Retest of fixed findings (terms in the statement of work)
Request a risk review about the Comprehensive Wireless Test

Enterprise Wireless Security

Custom

2-3 weeks

  • Multiple sites, scoped by location
  • 802.1X authentication testing
  • RADIUS server assessment
  • IoT device security testing
  • RF spectrum analysis
  • Guest network testing
  • Compliance gap analysis
  • Retest schedule agreed in the statement of work
Request a risk review about the Enterprise Wireless Security

Deliverables and proof

What you receive from a wireless penetration test

Every engagement is scoped and run to written rules of engagement. These are the deliverables, and the published engagements you can read before a call.

Deliverables

  • Executive summary with business impact analysis
  • Detailed technical findings and evidence
  • Network topology and wireless coverage maps
  • Risk-rated vulnerability assessment
  • Proof-of-concept demonstrations
  • Prioritized remediation roadmap
  • Secure configuration guidelines
  • Compliance mapping (PCI DSS, HIPAA, etc.)
  • Retest of fixed findings, with retest terms agreed in the statement of work

Retest: after you remediate, we retest the fixed findings and confirm in writing which are closed. Retest timing and terms are agreed in the statement of work.

See a sample finding (a fictional example, annotated, showing the report format).

Industries We Serve

Specialized wireless security testing for critical sectors

Healthcare

Secure medical devices, patient data, and HIPAA-compliant wireless infrastructure.

Financial Services

Protect sensitive financial data across wireless networks and mobile banking systems.

Retail & Hospitality

Secure guest WiFi, POS systems, and customer data in retail and hospitality environments.

Manufacturing

Test IIoT devices, wireless automation systems, and industrial control networks.

Wireless Penetration Testing FAQs

Common questions about wireless security testing and assessments

Still Have Questions?

Our cybersecurity experts are here to help. Get personalized answers and a free security consultation.

Secure Your Wireless Infrastructure

Don't let wireless vulnerabilities compromise your network security. Get expert testing today.