Every security policy and operational procedure that Requirement 10 calls for must meet four conditions: it is written down, it is kept current, it is actually followed in practice, and every affected party knows about it. This covers the policies and procedures behind audit logging, log protection, log review, log retention, time synchronization and detection of critical security control failures. Applies to all entities assessed against PCI DSS. Customized approach objective: the expectations, controls and oversight for logging and monitoring activities are set out and followed by the relevant staff, so that the work is repeatable, applied consistently and matches what management intends.
This control maps to 32 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 10.1.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 32 it maps to, and the evidence behind each claim, over MCP and REST.