LT-6 Configure log storage retention
Plan and configure log retention at each logging service according to compliance, regulatory and business requirements so logs are archived for the required period.
4
artefacts
2
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
- Retention requirement analysis per log type citing the obligation · SIEM / log platform
- Evidence logs older than the retention floor are still retrievable · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Retention policy configured at each logging service · Policy repository / GRC workspace
- Archive tier configuration and its access procedure · 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
- default retention accepted without checking the obligation
- retention set on the central workspace but not on individual services
- archived logs retained but no tested retrieval path
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 sheetLT-5 Centralize security log management and analysis · LT-7 Use approved time synchronization sources