← PCI DSS 4.0.1 · Req 10 — Log and monitor
10.4 — Audit logs are reviewed, using automated mechanisms
Requirement
Security events and logs of critical components and those that store, process or transmit cardholder data are reviewed at least once daily, using automated mechanisms such as a SIEM, and exceptions and anomalies are identified and addressed.
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.16 | Monitoring activities | monitoring siem |
| SOC 2 | CC7.2 | Monitoring for anomalies | monitoring siem |
| NIST CSF 2.0 | DE.CM-09 | Computing hardware, software and services are monitored | monitoring siem |
| SOC 2 | CC4.1 | Ongoing and separate evaluations | monitoring |
| ISO 27001 | A.5.7 | Threat intelligence | monitoring |
| ISO 27001 | A.7.4 | Physical security monitoring | monitoring |
| GLBA | 314.4(c)(8) | Monitoring and logging of authorised user activity | monitoring |
| NIST CSF 2.0 | DE.CM-01 | Networks and network services are monitored | monitoring |