10.4.1 Daily log review for critical systems
The following audit logs are reviewed at least daily: all security events, logs of all CDE system components, logs of critical systems, and logs of authentication, authorization, and accounting services.
5
artefacts
0
held by a system
3
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- SIEM dashboard showing daily review sign-off · SIEM / log platform
- Triage tickets from daily reviews · Ticketing / ITSM
- Sample of recent daily review records · Document repository
governing documentDocuments that govern the control
- Documented use cases reviewed daily · Document repository
- Reviewer assignment and rotation · Document repository
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Reviews skipped on weekends
- No sign-off
- Use cases stale
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.3.4 File integrity or change detection on logs · 10.4.1.1 Automated mechanisms for log review