CPS 234 para 25 Response Plan Content and Escalation Mechanisms
Response plans must set out the mechanisms for managing every stage of an incident from detection through to post incident review, and for escalating and reporting incidents to the Board and to those responsible for inci
3
artefacts
0
held by a system
1
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
- Post incident review records · Document repository
governing documentDocuments that govern the control
- Plan sections covering each incident stage · Policy repository / GRC workspace
- Escalation matrix with thresholds and recipients · 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
- Plans stop at containment with no post incident review
- Escalation path to the Board undefined
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 sheetCPS 234 para 24 Information Security Response Plans · CPS 234 para 26 Annual Review and Testing of Response Plans