10.3.4 File integrity or change detection on logs
File integrity monitoring or change-detection mechanisms are used on audit logs to ensure that existing log data cannot be changed without generating alerts.
5
artefacts
2
held by a system
1
at each review
moderate
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
- FIM tool configuration covering log paths · SIEM / log platform
- Sample FIM alerts on log modification tests · SIEM / log platform
periodic reviewEvidence produced at each review
- Periodic FIM health check evidence · SIEM / log platform
governing documentDocuments that govern the control
- Coverage list across systems · Policy repository / GRC workspace
- Procedure for FIM alert triage · Policy repository / GRC workspace
First move
Start with the 2 of 5 artefacts that already live in a system (SIEM / log platform); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- FIM not deployed on logs
- Alerts disabled
- Coverage gaps
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.3 Logs backed up to central server · 10.4.1 Daily log review for critical systems