SEF-03 Incident Response Plans
Maintain an approved security incident response plan that names the internal departments, affected cloud customers and business-critical relationships such as the supply chain that may be drawn in.
4
artefacts
0
held by a system
2
at each review
hard
to go live
Policy repository / GRC workspace
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
- Evidence customers and supply chain relationships are addressed · Document repository
- Distribution records for the current version · Document repository
governing documentDocuments that govern the control
- The approved incident response plan with its version · Policy repository / GRC workspace
- The stakeholder set named in the plan, internal and external · 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
- Plan names internal teams only, leaving customer and supplier involvement undefined
- Superseded versions still in circulation
- Plan approved once and never maintained against organisational change
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 sheetSEF-02 Service Management Policy and Procedures · SEF-04 Incident Response Testing