10.3.2 Logs protected from modification
Audit log files are protected to prevent modifications by individuals.
5
artefacts
3
held by a system
0
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
- SIEM configuration with append-only or WORM storage · SIEM / log platform
- Permissions export on local log files · Identity provider / directory
- Alerts on log modification attempts · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Procedure for log preservation · Policy repository / GRC workspace
- Sample integrity check results · Document repository
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
- Local logs writable
- No WORM storage
- No integrity alerts
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.1 Read access to logs restricted · 10.3.3 Logs backed up to central server