For every auditable event in 10.2.1.1 to 10.2.1.7, audit logs must record: the user identification; the type of event; the date and time; an indication of success or failure; where the event originated; and the identity or name of the data, system component, resource or service affected (for example, name and protocol). Applies to all entities. Customized approach objective: enough data is captured to recognise successful and failed attempts and to establish, for each event type in 10.2.1, the user, action, timing, location and method.
This control maps to 27 controls across 19 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.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 27 it maps to, and the evidence behind each claim, over MCP and REST.