ISO 27001 Wireless Security: What Auditors Actually Check
Wireless networks are one of the easiest places for an information security management system (ISMS) to come unstuck. They extend your network beyond the walls of your building, carry sensitive data through the air and are often configured once, then left alone for years. For organisations certified to ISO 27001, or working towards it, the WLAN is a regular point of interest during certification and surveillance audits.
ISO 27001 does not include a dedicated “wireless” control. Instead, auditors assess your wireless network against the same Annex A controls that govern the rest of your infrastructure, and they look for evidence that those controls are designed, implemented and working. This guide explains what ISO 27001 auditors typically check on the WLAN, and how to make sure you can show it.
How ISO 27001 auditors approach wireless security
It helps to understand what an auditor is, and is not, trying to do. A certification auditor will not usually walk your office with a spectrum analyser. Their job is to confirm that your ISMS identifies wireless risks, that you have chosen appropriate controls in your Statement of Applicability, and that you can produce evidence those controls operate in practice.
That means the audit is largely evidence-driven. Auditors will interview IT staff, review policies and configurations, and sample records such as access reviews, change tickets and vulnerability reports. Where the evidence is thin, they raise findings. The organisations that pass smoothly are those that already know what their wireless estate looks like and can prove it.
With the transition period from ISO 27001:2013 to ISO 27001:2022 now over, audits are assessed against the 2022 Annex A, which groups controls into organisational, people, physical and technological themes. Most wireless scrutiny falls under the technological controls.
What ISO 27001 auditors check on your wireless network
1. An accurate inventory of wireless assets
Control 5.9 requires an inventory of information and associated assets. For wireless, auditors expect you to know which access points, controllers and cloud management platforms you run, where they are, what firmware they use and who owns them.
Gaps here are common, especially after office moves or growth. Accurate network documentation makes this straightforward to evidence, and it also exposes any end-of-life network hardware that can no longer be patched.
2. Strong authentication and encryption
Controls 8.5 (secure authentication) and 8.24 (use of cryptography) apply directly to how users and devices join your WLAN. Auditors will look at which security protocols are in use and how credentials are managed.
Corporate networks are expected to use enterprise-grade authentication, typically WPA2-Enterprise or WPA3-Enterprise with 802.1X and individual user or certificate-based credentials. A single shared pre-shared key for staff, unchanged for years and known to former employees, is a likely nonconformity. Legacy protocols such as WEP or TKIP should not appear anywhere on the network.
3. Segregation of networks
Control 8.22 requires groups of information services, users and systems to be segregated. On a wireless network, this is where auditors focus on guest access, BYOD and IoT devices.
They will want to see that guests cannot reach internal systems, that personal devices are kept apart from corporate resources and that devices such as printers, cameras and building systems sit on their own segments. Guest and BYOD networks are a frequent source of findings, often because VLANs exist on paper but firewall rules between them are too permissive. Properly enforced network segmentation is the evidence auditors are looking for.
4. Network security and secure configuration
Controls 8.20 (networks security) and 8.9 (configuration management) cover how your wireless infrastructure is hardened and kept consistent. Auditors may ask for configuration baselines, evidence that management interfaces are restricted, and proof that default credentials have been changed on controllers and access points.
They will also look at change control. If wireless settings are altered without a recorded change, approval and rollback plan, expect questions.
5. Detection of rogue and unauthorised devices
An unauthorised access point plugged into a network port can bypass every other control you have. Auditors will often ask how you would detect one, and whether you have ever checked.
Wireless intrusion detection or prevention features, regular scans and documented investigations of anything unexpected all provide good evidence. A periodic wireless security audit to find rogue access points and unsecured devices demonstrates that the control works in practice, not just in policy.
6. Vulnerability and patch management
Control 8.8 requires technical vulnerabilities to be identified and addressed. Wireless controllers and access points receive security advisories like any other network device, and auditors will want to see that you track them and apply firmware updates in a timely way.
A spreadsheet showing firmware versions alongside vendor advisories, together with change records for upgrades, is usually enough. Hardware that is out of vendor support makes this control very difficult to satisfy.
7. Logging and monitoring
Controls 8.15 (logging) and 8.16 (monitoring activities) expect you to record and review security-relevant events. For wireless, that includes authentication failures, administrative logins, configuration changes and rogue device alerts.
Auditors will check that logs are retained, protected from tampering and actually reviewed. Sending wireless logs to a central platform, ideally monitored by a security operations centre, shows that events are acted upon rather than simply stored.
8. Access rights and supplier oversight
Control 5.18 covers access rights, so auditors may sample who has administrative access to the wireless platform and when that access was last reviewed. Leavers with active admin accounts are a classic finding.
Many organisations now manage WiFi through cloud platforms or a managed service provider. Controls 5.19 to 5.23 cover supplier relationships and cloud services, so be ready to show how you assessed and monitor any third party with access to your wireless environment.
Common wireless findings in ISO 27001 audits
Certain issues come up again and again. These include shared passwords on corporate SSIDs, guest networks that can reach internal resources, no process for detecting rogue access points, out-of-date firmware, incomplete asset registers and wireless logs that nobody reviews. Most are not difficult to fix, but each one undermines confidence in your wider ISMS.
How to prepare your WLAN for an ISO 27001 audit
The most effective preparation is an independent review before the auditor arrives. A WiFi audit assesses configuration, authentication, segmentation and rogue device exposure, then gives you a prioritised list of fixes and the evidence to support your Statement of Applicability.
Wireless is also one part of a bigger picture. A broader network audit can support ISO 27001, NIST and GDPR compliance across your whole infrastructure, and it is worth understanding the difference between a network audit and a penetration test so you commission the right assurance for each control.
Get audit-ready with Opticore
Opticore helps regulated organisations in financial services, legal and insurance secure and evidence their wireless networks. Our engineers combine wireless site survey services with security assessment, so you get a clear view of both performance and compliance in a single engagement.
If you have an ISO 27001 certification or surveillance audit on the horizon, talk to our team about a wireless security review that gives your auditor the evidence they need.