● Talk to a security engineer: +92 323 8295031info@protonyte.com  ·  PCSF batch enrolling now

Wireless penetration testing: the network anybody in the car park can see

Every other part of your perimeter needs a cable or a login. Your Wi-Fi is broadcasting past the walls to whoever is sitting outside with a laptop. Protonyte tests WPA2, WPA3 and 802.1X enterprise networks on site in Karachi and on site across the Gulf: what can be captured, what can be cracked, what a fake access point can collect, and whether the guest network really is separate from everything else.

the wall access point the car park

ENGAGEMENT SCOPEon site, 2 - 5 days

WPA2 Personal and EnterpriseIN SCOPE
WPA3 and transition-mode weaknessesIN SCOPE
802.1X / RADIUS authenticationIN SCOPE
Rogue and evil-twin access pointsIN SCOPE
Guest network segregationIN SCOPE
Physical site surveyIN SCOPE
// the basics

What a wireless test is for

Wireless fails in two ways, and they need different answers. The first is the network itself: a pre-shared key that can be captured and cracked, an enterprise setup where the client never checks the server certificate, a WPA3 network left in transition mode so it can still be downgraded.

The second is the people. A laptop that has connected to your office Wi-Fi once will usually connect to anything using the same name. Stand a fake access point outside the building with that name and a stronger signal, and devices come to you. What they hand over depends entirely on how the genuine network was configured - which is the part of the report that tends to surprise people.

  • 01On site, with real radiosWireless cannot be tested remotely. We come to the building with the equipment.
  • 02Enterprise, not just the password802.1X, certificate validation and RADIUS behaviour, which is where enterprise networks actually leak.
  • 03Guest network provedWe connect as a guest and try to reach the corporate side, which is a PCI DSS requirement as well as common sense.
  • 04Coverage mappedWhere your signal actually reaches, including the street and the floors you do not own.
// coverage

What we go after

A survey first, so we are testing the network that exists rather than the one on the documentation, then the attacks that matter for how yours is configured.

// what is on the air

Survey and discovery

Every network and device broadcasting in and around your site.

  • All SSIDs, including hidden ones
  • Encryption and authentication per network
  • Signal reach beyond your walls
  • Unauthorised access points on your network
// the key

WPA2 and WPA3 personal

Whether the passphrase protecting the network can be recovered.

  • Handshake and PMKID capture
  • Offline cracking against realistic wordlists
  • WPA3 transition-mode downgrade
  • WPS and vendor setup features
// the enterprise setup

802.1X and RADIUS

Where enterprise wireless usually goes wrong.

  • EAP method and certificate validation
  • Credential capture through a fake RADIUS
  • Machine versus user authentication
  • Fallback to a weaker method
// the fake one

Rogue and evil twin

A network with your name on it, run by somebody else.

  • Evil-twin and karma attacks
  • Captive portal cloning
  • Client probe behaviour and auto-connect
  • What devices disclose before connecting
// the walls

Segregation

What a connected device can reach once it is on.

  • Guest to corporate reachability
  • Client isolation on the guest network
  • Wireless into cardholder or sensitive scope
  • Management interfaces over Wi-Fi
// the hardware

Access points and controllers

The devices themselves, which are rarely reviewed after install.

  • Controller and AP management access
  • Default and shared credentials
  • Firmware level and known issues
  • Configuration drift between sites
// methodology

How the work runs

  1. 1

    Scope and site

    Which buildings, which networks, and what we may do with a client device that connects to us.

    • Sites and floors in scope
    • Networks owned by you, and neighbours excluded
    • Whether client-side attacks are permitted
    • Written authorisation and a site contact
  2. 2

    Survey

    A walk of the site with the radios on, inside and outside.

    • Full SSID and BSSID inventory
    • Encryption and authentication recorded
    • Signal reach mapped beyond the perimeter
    • Rogue devices identified
  3. 3

    Attack the network

    Against the configuration we found, not a generic list.

    • Handshake and PMKID capture
    • Enterprise credential capture attempts
    • Downgrade and transition weaknesses
    • Management plane access
  4. 4

    Attack the clients

    Only where you have agreed to it, and only with your own devices.

    • Evil twin with your SSID
    • Captive portal credential capture
    • Device auto-connect behaviour
    • What was disclosed, and by which devices
  5. 5

    Report and retest

    What reached outside, what was crackable, what the fake access point collected, and how to close each one.

    • Findings with capture evidence
    • Coverage map of where the signal reaches
    • Configuration changes in priority order
    • Retest and closure summary
// the deliverable

What you are left holding

Two documents and a conversation. Written so the person who signs the invoice and the person who writes the fix can both use them.

  • Executive summary in plain language, with the business risk first
  • Technical findings with the evidence that proves each one
  • CVSS score and a risk rating that reflects your business, not a template
  • Remediation written for the stack you actually run
  • A free retest, and a closure summary you can hand to a customer
  • A debrief call with the tester who did the work, not an account manager
Ask for a sample report
// the standards

Measured against something

The work follows NIST SP 800-115, NIST SP 800-153, PCI DSS wireless requirements and IEEE 802.11, so the coverage can be checked rather than taken on trust, and the report maps to what your auditor or your enterprise customer already recognises.

This page is one part of our penetration testing service. Where a finding needs a different kind of engagement to answer properly, we say so in the report rather than selling you the test we happen to be running.

// faq

Common questions

Can wireless testing be done remotely?

No. Wi-Fi is radio, so somebody has to be within range with the right hardware. We test on site in Karachi as standard and travel for engagements in the UAE, Saudi Arabia and Qatar, usually combined with an internal network test in the same visit to keep the travel on one invoice.

We use WPA3. Is there anything to find?

Often, yes. Most WPA3 deployments run in transition mode so older devices still work, and transition mode can be pushed back down to WPA2. Beyond that, the enterprise side - certificate validation on the clients, RADIUS behaviour, what a device does when it sees a familiar name - is unchanged by WPA3.

Will you disconnect our staff?

Deauthentication is sometimes needed to capture a handshake, and it is brief and targeted. We agree in advance whether it is allowed at all, and if your environment cannot tolerate it we use passive capture and PMKID methods instead.

Do you test the guest network?

Always, and it is frequently where the finding is. We connect as an ordinary guest and try to reach the corporate network, other guests, and the management interfaces of the access points. PCI DSS treats wireless as in scope and expects that boundary to be proved.

What about access points we did not install?

Finding them is part of the job. A rogue access point plugged into a wall port by a well-meaning employee bypasses every other control you have, and the survey is what turns it up.

// start here

Let's protect your business together.

Tell us what you need tested. Our team will reply with a clear scope and quote.

By submitting, you agree to our Terms of Use and Privacy Statement.