12.10.6 IRP refined based on lessons learned
The security incident response plan is modified and evolved according to lessons learned and to incorporate industry developments.
5
artefacts
1
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
- IRP change log linked to lessons · SIEM / log platform
periodic reviewEvidence produced at each review
- Post-incident review documents with lessons · Document repository
- Industry threat intel review records · Document repository
governing documentDocuments that govern the control
- Approval of updates · Document repository
- Communication of changes to responders · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your SIEM / log platform on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Lessons learned skipped
- No industry input
- IRP unchanged
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 sheet12.10.5 IRP includes monitoring and response to security control alerts · 12.10.7 Response procedures for PAN detection in unexpected locations