LOG-07 Logging Scope
Decide, document and implement which system events and metadata are to be logged, and revisit that scope at least annually and whenever the threat picture changes.
4
artefacts
2
held by a system
1
at each review
easy
to go live
SIEM / log platform
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- The documented logging scope listing event types per system · SIEM / log platform
- Configuration evidence that the scope is implemented · SIEM / log platform
periodic reviewEvidence produced at each review
- Annual review record and reviews triggered by threat changes · SIEM / log platform
governing documentDocuments that govern the control
- The rationale for events excluded from scope · Policy repository / GRC workspace
First move
Automate the pull from your SIEM / log platform. Retention and alert rules exported from the SIEM; review evidence is the closed-alert record with reviewer and time.
Common gaps auditors find
- Scope defined by what the tooling produces by default rather than by decision
- Scope documented but not implemented in several systems
- No review after a significant change in the threat environment
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 sheet