CPS 234 para 26 Annual Review and Testing of Response Plans
Information security response plans must be reviewed and tested annually to confirm they remain effective and fit for purpose.
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
- Evidence of fitness for purpose conclusions · Document repository
governing documentDocuments that govern the control
- Annual review and test records for response plans · Policy repository / GRC workspace
- Exercise reports and resulting plan updates · 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 reviewed but never exercised
- Test findings not fed back into the plans
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 25 Response Plan Content and Escalation Mechanisms · CPS 234 para 27 Systematic Control Testing Program