CPS 234 para 24 Information Security Response Plans
The entity must maintain response plans covering the information security incidents it considers could plausibly occur.
3
artefacts
0
held by a system
0
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
none for this control
governing documentDocuments that govern the control
- Documented response plans · Policy repository / GRC workspace
- Plausible incident scenario analysis supporting plan coverage · Policy repository / GRC workspace
- Version and approval history · Document repository
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
- Single generic plan with no scenario basis
- Plausible scenarios identified but not planned for
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 23 Detection and Response Mechanisms · CPS 234 para 25 Response Plan Content and Escalation Mechanisms