Physical controls, logical controls, or a mix of the two must be applied within the facility to stop publicly accessible network jacks from being used. The guidance offers examples such as disabling jacks in public or visitor-accessible areas and enabling them only when network access is explicitly approved, or escorting visitors at all times wherever active jacks exist, and says whatever approach is used should stop any person or device lacking explicit authorization from connecting. Applicability: all entities. Objective under the customized approach: unauthorized devices cannot connect to the network of the entity from public areas of the facility.
This control maps to 28 controls across 17 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 9.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 28 it maps to, and the evidence behind each claim, over MCP and REST.