CP-4 Contingency plan testing
Requires the contingency plan to be tested at a defined frequency using defined test types to establish that the plan works and that people are ready to execute it, the test results to be reviewed, and corrective action
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
- Test report with results, observations and participants · Document repository
- Defined test types and frequency, and evidence they were met · Document repository
governing documentDocuments that govern the control
- Test plan and scenario documentation for each exercise · Policy repository / GRC workspace
- Corrective actions raised, tracked and closed following the test · 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
- Tabletop exercise substituted for the technical failover test the plan requires
- Results recorded but corrective actions never tracked to closure
- Test scope avoids the components most likely to fail
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 sheet