← PCI DSS 4.0.1 · Req 10 — Log and monitor
10.2 — Audit logs capture user activity and security events
Requirement
Audit logs are enabled and active for all system components and cardholder data, capturing individual user access to cardholder data, all actions by administrators, access to audit logs, invalid access attempts, changes to identification and authentication credentials, and creation or deletion of system-level objects, with sufficient detail for each event.
What the engine looks for
Every group below must be satisfied — by an affirmative statement, not a plan, a hedge or a denial — for the control to count as covered. A term ending in … matches any word it begins. Supporting terms do not change the verdict — they raise confidence and distinguish a policy that names a mechanism from one that gestures at a category.
Finding any of these outranks coverage — a policy that admits the gap is worse than silence.
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| ISO 27001 | A.8.15 | Logging | logging |
| NIST CSF 2.0 | PR.PS-04 | Log records are generated and made available for monitoring | logging |
| SOC 2 | CC2.1 | Quality information for internal control | logging |
| HIPAA | 164.312(b) | Audit controls (R) | logging |
| GLBA | 314.4(c)(8) | Monitoring and logging of authorised user activity | logging |
| SOC 2 | CC7.2 | Monitoring for anomalies | logging |
| ISO 27001 | A.5.28 | Collection of evidence | logging |
| HIPAA | 164.308(a)(1)(ii)(D) | Information system activity review (R) | logging |