← NIST CSF 2.0 · PROTECT — Platform Security
PR.PS-04 — Log records are generated and made available for monitoring
high
logging
Requirement
Log records are generated and made available for continuous monitoring.
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 trail
Required element 2 — any one of
centralis…centraliz…aggregat…availableforwardedretentionretain
Supporting terms — specificity signals
siemcloudtrailimmutable90 days12 monthstime sync
Contradiction markers
Finding any of these outranks coverage — a policy that admits the gap is worse than silence.
logging is disabled
logs stay on the host
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 |
| PCI DSS 4.0.1 | 10.2 | Audit logs capture user activity and security events | 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 |