Audit logs must record each instance of an individual user reaching cardholder data. Applies to all entities. The guidance notes that such a record links access to a specific user and helps show which accounts may have been misused or compromised, including accounts an attacker has created. Customized approach objective: every access to cardholder data by an individual user leaves a record.
This control maps to 38 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.2.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 38 it maps to, and the evidence behind each claim, over MCP and REST.