Design, implement and maintain in-scope wireless networks so that incidents cannot spread to other control systems, only authorised people, processes and devices can use them, and information in transit cannot be read or altered: use industry-standard cryptography and key lengths, keep wireless devices off other networks (no dual-homing), build wireless as separate segments protected as sections 4.2.1 plus 4.2.2 require, install and configure access points so access is controllable, and identify and authenticate every user, process or device on the link.
This control maps to 1 controls across 1 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.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.