Audit log files, including logs from external-facing technologies, must be promptly backed up to one or more secure, central, internal log servers or to other media that is hard to modify. Applies to all entities. The guidance gives wireless, DNS servers, mail servers and network security controls as examples of external-facing sources, and notes that each entity chooses how to back up logs, whether written directly, offloaded or copied to the secure store. Objective under the customized approach: the stored records of activity are held securely in a central place so they cannot be modified without authorization.
This control maps to 39 controls across 16 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.3 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 39 it maps to, and the evidence behind each claim, over MCP and REST.