IR-7 Post-incident activity - conduct lesson learned and retain evidence
Conduct lessons learned periodically and after major incidents, and retain incident evidence for the period defined in the incident handling standard.
4
artefacts
0
held by a system
2
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Post-incident review records with actions and owners · Document repository
- Chain of custody handling for retained evidence · Document repository
governing documentDocuments that govern the control
- Tracking of those actions through to closure · Document repository
- Evidence retention standard and storage location · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- reviews held but actions never tracked
- evidence deleted with normal log retention before the retention period
- reviews only after major incidents so recurring small incidents teach nothing
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 sheetIR-6 Containment, eradication and recovery - automate the incident handling · LT-1 Enable threat detection capabilities