CP-2 Contingency plan
Requires a contingency plan that identifies essential mission and business functions and their contingency requirements, sets recovery objectives, priorities and metrics, assigns roles and contacts, addresses operating t
5
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
- Review and update history including changes after tests or incidents · Document repository
governing documentDocuments that govern the control
- Approved contingency plan with recovery objectives, priorities and metrics · Policy repository / GRC workspace
- Business impact analysis identifying essential functions and dependencies · Document repository
- Distribution list and evidence the plan reached the defined recipients · Policy repository / GRC workspace
- Evidence of coordination with incident response and related organizational plans · 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 lists systems but never identifies the business functions they support
- Contact details stale, naming people who left the organization
- Plan updated after tests but the revised version never redistributed
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 sheetCP-1 Policy and procedures for contingency planning · CP-3 Contingency training