EvidenceSheet
CSA CCM v4.1 · BCR - Business Continuity Management and Operational Resilience

BCR-01 Business Continuity Management Policy and Procedures

Policies and procedures for continuity management and for operational resilience are approved, documented, communicated, applied, evaluated and kept current, with a review and update at least once a year and after significant changes.

Source: CSA CCM v4.1, BCR-01. 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.

4
artefacts
1
held by a system
1
at each review
moderate
to go live
SIEM / log platform
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

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

  • Policy review log with yearly and change-triggered reviews · SIEM / log platform

periodic reviewEvidence produced at each review

  • Communication records to staff with continuity roles · Identity provider / directory

governing documentDocuments that govern the control

  • Approved business continuity and operational resilience policy with owner and review date · Policy repository / GRC workspace
  • Supporting continuity procedures referenced by the policy · Policy repository / GRC workspace

First move

Start with the 1 of 4 artefacts that already live in a system (SIEM / log platform); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

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

AIS-08 API Security · BCR-02 Risk Assessment and Impact Analysis