Consoles located in sensitive areas must be locked whenever they are not being used, so that no one without authorization can use them. The guidance explains that locking console sessions prevents unauthorized people from viewing sensitive information, changing system configurations, introducing vulnerabilities or destroying records. Applicability: all entities that have consoles located in sensitive areas. Customized approach objective: physical consoles inside sensitive areas cannot be operated by unauthorized personnel.
This control maps to 25 controls across 10 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.4 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 25 it maps to, and the evidence behind each claim, over MCP and REST.