BCR-04 Business Continuity Planning
A business continuity plan is approved, documented, communicated, applied, evaluated and kept current, grounded in what the resilience strategies and capabilities produced.
Source: CSA CCM v4.1, BCR-04. 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 review records and change history · Policy repository / GRC workspace
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Approved business continuity plan with version, owner and distribution list · Policy repository / GRC workspace
- Traceability from the plan to resilience strategies and BIA outputs · Policy repository / GRC workspace
- Copies of the plan available to responders offline or out of band · Policy repository / GRC workspace
First move
Common gaps auditors find
- Plan not derived from the current strategy and BIA
- Plan stored only on systems that would be unavailable in a disruption
- Contact lists and roles in the plan out of date
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