10.3.3 Logs backed up to central server
Audit log files, including those for external-facing technologies, are promptly backed up to a secure, central, internal log server or other media that is difficult to modify.
5
artefacts
2
held by a system
0
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
- Sample of recent log entries forwarded · SIEM / log platform
- Backup retention configuration · Backup / DR tooling
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Architecture diagram of log forwarding · Policy repository / GRC workspace
- SIEM ingestion dashboards by source · Policy repository / GRC workspace
- Coverage matrix of external-facing systems · 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
- External systems not forwarding
- Forwarding gaps unnoticed
- No central log server
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.2 Logs protected from modification · 10.3.4 File integrity or change detection on logs