The entity manages wireless access points, authorized or not, by: testing for the presence of Wi-Fi access points; detecting and identifying every authorized and unauthorized access point; performing this testing, detection and identification at least every three months; and, where automated monitoring is in place, notifying personnel through generated alerts. Guidance (examples and good practice): methods may include wireless scans, physical or logical inspection, network access control or wireless IDS/IPS, combined as the environment's size and complexity dictate. Applicability: the requirement still applies where policy bans wireless technology, and the chosen methods must be able to find both authorized and unauthorized devices, including rogue devices plugged into equipment that is itself authorized. Objective under the customized approach: rogue wireless access points are found and dealt with on a periodic basis.
This control maps to 39 controls across 14 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
PCI DSS 4.0 11.2.1 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of PCI DSS 4.0 your existing evidence covers. Hold ISO 27001:2022 and 139 of 280 PCI DSS 4.0 controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 415 were rejected on the ISO 27001:2022 pair alone.
The graph holds this control, the 39 it maps to, and the evidence behind each claim, over MCP and REST.