The entity keeps an up-to-date inventory of the wireless access points it has authorized, and each entry carries a documented business justification. Guidance (purpose): the inventory helps administrators respond quickly when rogue devices are detected. Guidance (good practice): also record known neighbouring access points that appear in scans but are not attached to the entity's network, noting how it was confirmed they can be disregarded, and handle any rogue access point posing a threat to the CDE under the Requirement 12.10.1 incident response plan. Objective under the customized approach: rogue wireless access points cannot be confused with authorized ones.
This control maps to 20 controls across 12 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.2 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 20 it maps to, and the evidence behind each claim, over MCP and REST.