10.2.1.7 Logs capture creation and deletion of system-level objects
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.
Source: PCI DSS v4.0.1, 10.2.1.7. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open PCI DSS v4.0.1 in the compliance library.
Version 4.0.1 is the active version; 4.0 has been retired. Appendix A1 applies only to multi-tenant service providers, A2 only to card-present POS POI terminals that still use SSL or early TLS, and A3 only when a payment brand or acquirer requires it. Which requirements apply to you follows your validation type.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Audit rules covering creation and removal of services, drivers, scheduled jobs and system files · Policy repository / GRC workspace
- Database DDL audit settings for object creation and drops · Policy repository / GRC workspace
- Sample log entries of system-level object creation or deletion · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Mapping of system-level object types the entity has defined per platform · Document repository
First move
Common gaps auditors find
- Entity has never defined what counts as a system-level object on each platform
- DDL changes to cardholder data databases not audited
- Container or serverless environments lack equivalent object logging
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet10.2.1.6 Logs capture initialization and stopping of audit logs · 10.2.2 Required details recorded for each auditable event