Audit logs must be covered by file integrity monitoring or by change-detection tooling so that existing log data cannot be altered without an alert being raised. Applies to all entities. As good practice, the guidance recommends that the tooling alert when stored log content or log files are altered or removed, but not when new entries are appended. Objective under the customized approach: nobody can change the stored records of activity without an alert.
This control maps to 30 controls across 14 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.3.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 30 it maps to, and the evidence behind each claim, over MCP and REST.