Requirement
Logs that record activities, exceptions, faults and other relevant events shall be produced, stored, protected and analysed.
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.
Required element 1 — any one of
logloggingaudit logaudit trail
Required element 2 — any one of
retainretentioncentralis…centraliz…protectreview
Supporting terms — specificity signals
immutabletamper90 days12 monthssiemcorrelat…clock sync
Contradiction markers
Finding any of these outranks coverage — a policy that admits the gap is worse than silence.
logging is not enabled
logs are not retained
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| PCI DSS 4.0.1 | 10.2 | Audit logs capture user activity and security events | 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 |
| PCI DSS 4.0.1 | 10.5.1 | Audit log history retained for 12 months | logging |
| PCI DSS 4.0.1 | 10.6 | Time synchronisation | 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 |