CP-1 Policy and procedures for contingency planning
Requires a contingency planning policy and supporting procedures to be developed, approved, disseminated to defined personnel, owned by a named official, and reviewed and updated on a defined frequency and after defined
5
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
- Approved contingency planning policy with scope, approver and date · Policy repository / GRC workspace
- Evidence the contingency planning policy reached the personnel or roles it defines · Policy repository / GRC workspace
- Written designation of the official accountable for the contingency planning policy and procedures · Policy repository / GRC workspace
- Procedures supporting plan development, testing and activation · Policy repository / GRC workspace
- Review record for the contingency planning policy and procedures against the defined frequency and triggering events · 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
- Policy covers disaster recovery of infrastructure but not business function continuity
- Review only after an incident rather than at a defined cadence
- Policy silent on services delivered by third parties
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 sheetCM-14 Signed Components. Prevent the installation of [organization-defined] without verification that the component has been digitally signed using a certificate that is recognized and approved by the organization · CP-2 Contingency plan