GS-8 Define and implement backup and recovery strategy
Define and implement a backup and recovery strategy with documented guidance, policy and standards including recovery time and recovery point objectives.
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
- Evidence recovery testing is scheduled against those objectives · Backup / DR tooling
governing documentDocuments that govern the control
- Backup and recovery strategy document · Policy repository / GRC workspace
- Recovery time and recovery point objectives per service tier · Policy repository / GRC workspace
- Backup policy and standard derived from the objectives · 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
- backups configured with no stated recovery objective
- objectives set but never tested against actual restore times
- strategy omits platform and software service data
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 sheetGS-7 Define and implement logging, threat detection and incident response strategy · GS-9 Define and implement endpoint security strategy