Overview
Wireless testing needs someone within range of your access points, and we deliver from India, so on-site work for US locations is planned case by case. Tell us the sites, building types and any operational wireless at scoping, and we will say plainly whether and how we can cover them before you sign. Remote parts of the review, such as controller configuration, can run in the meantime.
Wireless is the one part of your network an attacker can reach without a cable or a phished click. Signal leaks into parking lots, neighboring units and the street, which makes the strength of your authentication and encryption the only thing standing between an outsider and an internal foothold. A wireless assessment is carried out on site, where that real signal footprint and the devices connecting to it can actually be observed.
We assess the networks you run and the ways they can be abused. For enterprise authentication we test how clients validate the network they join and whether their credentials can be captured or relayed; for pre-shared networks we test the strength of the key and the handshake. We look for rogue and evil-twin exposure, where a client can be lured onto an attacker-controlled network, and we check whether guest, corporate and operational wireless are truly separated or quietly share a path.
The result ties wireless weaknesses to business impact. A weak key or a client that trusts any network is only serious if it leads somewhere, so we show whether wireless access reaches the internal LAN and what it exposes once there. Findings are scored with CVSS v4.0 and paired with practical fixes, stronger authentication, client configuration, proper isolation, that an on-site network team can apply.
How US engagements run
- Delivered remotely from India, 9.5 hours ahead of US Eastern in US daylight time and 10.5 hours in winter; calls and testing windows are set around your time zone at scoping
- Fixed-price proposals in US dollars, with scope, dates and the free retest written in before any work begins
- Written authorization signed by someone with authority over every target, because the federal Computer Fraud and Abuse Act and state laws make permission the dividing line
- Reports that name the requirement a test supports, such as PCI DSS 11.4, the FTC Safeguards Rule or SOC 2, without claiming a QSA, ASV or C3PAO role we don't hold
What's included
Our approach
- Site planningWe agree locations, networks and timing for an on-site assessment.
- SurveyWe map the wireless footprint, the networks present and the devices connecting.
- Authentication testingWe test encryption, authentication and client validation for each network.
- Rogue & isolationWe assess evil-twin exposure and whether network separation holds.
- Report & debriefFindings are tied to LAN impact, scored and explained to your network team.
What you receive
- Inventory of wireless networks and their exposure
- Encryption and authentication findings with CVSS v4.0 scores
- Rogue and evil-twin exposure assessment
- Isolation and segmentation test results
- Free retest of fixed issues and an attestation letter
Standards & frameworks
- PTES
- NIST SP 800-115
- OWASP WSTG
- MITRE ATT&CK
- CIS Benchmarks
- CVSS v4.0
- PCI DSS v4.0.1 Req. 11.4
- NIST SP 800-171
Frequently asked questions
Does wireless testing have to be on site?
Yes. Wireless is a physical, signal-based medium, so meaningful testing of your encryption, rogue exposure and real coverage requires a tester present at your location. We agree the sites and timing in advance and work around your operations.
Will you knock users off the network?
We avoid disruption wherever possible and schedule any technique that could affect connectivity with your team. Some targeted tests briefly involve specific devices we agree in advance, never a blanket disruption of your users during business hours.
What do you need from us to start?
Access to the sites in scope, a list of the wireless networks you operate, and a technical contact who knows the environment. Letting us know about any critical operational wireless beforehand means we can treat it with extra care.
Does an internal and external test cover PCI DSS Requirement 11.4?
It can, when scoped for it. PCI DSS v4.0.1 wants penetration tests from inside and outside the network every year and after significant changes, following a documented methodology, plus proof that segmentation holds. We aren't a QSA or ASV, so quarterly ASV scans and the assessment itself stay with those firms.
Can you test our US networks without traveling?
Network, Active Directory, cloud and Kubernetes testing run remotely through a VPN account, jump host or small test device you place on the network. Wireless and hardware work need someone near the equipment; tell us the sites at scoping and we'll say plainly whether and how we can cover them.