CP-1 Policy and Procedures
Develop and review contingency planning policy at least annually.
6
artefacts
0
held by a system
3
at each review
hard
to go live
Document repository
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
- Annual tabletop and full failover test reports · Backup / DR tooling
- Alternate processing site contract and capacity attestation · Vendor register / contract repository
- Restoration test logs with success criteria signed off · Backup / DR tooling
governing documentDocuments that govern the control
- Control implementation statement for CP-1 citing the system mission and inheritance from common controls · Document repository
- Backup schedule, retention, and offsite or immutable copy evidence · Policy repository / GRC workspace
- Business impact analysis identifying critical systems · 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
- Backups taken but restore tests never performed end to end
- RTO and RPO targets undefined for tier two systems
- Tabletop exercises lack participation from business owners
- Alternate site capacity not validated against current load
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