BCR-08 Backup
Backups are taken periodically, their confidentiality, integrity and availability are protected, and restoration from backup is checked to support resilience.
Source: CSA CCM v4.1, BCR-08. 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 CSA CCM v4.1 in the compliance library.
Version 4.1 adds 11 controls (among them API security, log sanitisation and a service bill of materials) and renumbers several domains. CSA accepts v4.0.x during its transition; if your STAR assessment is still on v4.0.1, check the numbering against it.
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 job reports showing successful completion for a sample period · Backup / DR tooling
- Encryption and access control settings for backup storage · Backup / DR tooling
- Restore test records with date, data restored and outcome · Backup / DR tooling
- Immutable or offsite backup configuration · Backup / DR tooling
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Backup policy defining scope, frequency and retention · Policy repository / GRC workspace
First move
Common gaps auditors find
- Backups never restored to prove they work
- Backup storage reachable with the same credentials as production
- Some data stores missing from backup scope
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