BR-4 Regularly test backup
Perform periodic data recovery tests against backups to verify the backup configuration and the availability of backup data meet the defined recovery time and recovery point objectives.
4
artefacts
1
held by a system
0
at each review
moderate
to go live
Backup / DR tooling
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Defect log and remediation from failed tests · Backup / DR tooling
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Restore test schedule and completed test records · Policy repository / GRC workspace
- Measured restore time compared with the recovery time objective · Policy repository / GRC workspace
- Data currency of the restored copy compared with the recovery point objective · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (Backup / DR tooling); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- backups verified only by job success status, never by actual restore
- tests restore a small sample that does not exercise the real recovery path
- measured restore time never compared with the stated objective
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-3 Monitor backups · DP-1 Discover, classify, and label sensitive data