BCR-08 Backup
Back up cloud-held data on a defined cycle, protect the confidentiality and integrity of the backups, and prove by restore testing that the data can actually be recovered.
4
artefacts
1
held by a system
1
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
- Backup encryption and access control configuration · Backup / DR tooling
periodic reviewEvidence produced at each review
- Restore test results with date, scope and outcome · Backup / DR tooling
governing documentDocuments that govern the control
- Backup schedules and job success records · Policy repository / GRC workspace
- Retention settings matched to 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 running successfully but never restore tested
- Backups readable by the same credentials that could destroy production
- Restore tested for one system and the result generalised to all
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 sheet