CP-10 System recovery and reconstitution
Requires the system to be recoverable and reconstitutable to a known state within an organization-defined period consistent with its recovery time and recovery point objectives after disruption, compromise or failure.
4
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
- Recovery test results showing objectives met within the defined period · Backup / DR tooling
governing documentDocuments that govern the control
- Documented recovery time and recovery point objectives for the system · Policy repository / GRC workspace
- Recovery procedures describing return to a known and secure state · Policy repository / GRC workspace
- Validation that controls are restored, not only functionality · 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
- Objectives stated by the business but never tested against actual recovery times
- Recovery restores service while security controls remain disabled from the recovery process
- Reconstitution after compromise not covered, only recovery after outage
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-9 System backup · CP-11 Alternate Communications Protocols. Provide the capability to employ [organization-defined] in support of maintaining continuity of operations