Every time a system-level object is created or deleted, the audit logs must record it. Applies to all entities. The guidance explains that malicious software frequently adds or swaps system-level objects in order to take over of a function, and that logging these events makes it easier to judge whether a change was authorized. Objective under the customized approach: changes suggesting a system has been altered away from its intended function leave a record.
This control maps to 20 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.2.1.7 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 20 it maps to, and the evidence behind each claim, over MCP and REST.