BR-3 Monitor backups
Monitor backups so all business-critical protectable resources are confirmed compliant with the defined backup policy and standard.
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
- Remediation records for unprotected critical resources · Backup / DR tooling
governing documentDocuments that govern the control
- Backup compliance report listing protectable resources and their protection state · Policy repository / GRC workspace
- 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
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
- 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