BR-3 Monitor backups
Monitor backups so all business-critical protectable resources are confirmed compliant with the defined backup policy and standard.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), BR-3. 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
- Backup compliance report listing protectable resources and their protection state · Backup / DR tooling
periodic reviewEvidence produced at each review
- Remediation records for unprotected critical resources · Backup / DR tooling
governing documentDocuments that govern the control
- Alerting on failed or missed backup jobs · Policy repository / GRC workspace
- Reconciliation between the asset inventory and protected resources · Policy repository / GRC workspace
First move
Common gaps auditors find
- backup jobs monitored but resource coverage never reconciled against the inventory
- new resources created without backup and never detected
- failed jobs logged but no alert reaches an owner
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 sheetBR-2 Protect backup and recovery data · BR-4 Regularly test backup