BCR-09 Disaster Response Plan
A disaster response plan for recovering from natural and man-made disasters is approved, documented, communicated, applied, evaluated and kept current, and it is updated yearly at a minimum or on significant changes.
Source: CSA CCM v4.1, BCR-09. 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
- Plan update history showing yearly and change-triggered revisions · Backup / DR tooling
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Approved disaster response plan covering natural and man-made scenarios · Policy repository / GRC workspace
- Roles and call tree for disaster response · Policy repository / GRC workspace
- Alternate site or region recovery procedures · Policy repository / GRC workspace
First move
Common gaps auditors find
- Plan covers technical failover only, not facility-level disasters
- Plan not revised after moving data centres or regions
- Responders not trained on the plan
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