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.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), GS-8. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark) in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
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
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