What evidence do auditors commonly ask for on BCR-02 Risk Assessment and Impact Analysis?

Business impact analysis with recovery time and recovery point objectives per service; Continuity risk assessment identifying disruption scenarios and likelihood; Criteria for continuity strategies derived from the BIA (for example maximum tolerable downtime); Approval and review dates of the BIA and risk assessment; Records of BIA updates following new services or major changes.

What is the most common gap auditors find on BCR-02?

BIA performed once and never refreshed

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

`BCR-02` Risk Assessment and Impact Analysis

The organisation works out the impact of business disruptions and the risks behind them, and uses that to set the criteria for building continuity and resilience strategies and capabilities. The risk assessment and impact analysis are revisited every year as a minimum and after significant changes.

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

artefacts

held by a system

at each review

hard

to go live

Policy repository / GRC workspace

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

none for this control

periodic reviewEvidence produced at each review

Business impact analysis with recovery time and recovery point objectives per service · Policy repository / GRC workspace
Continuity risk assessment identifying disruption scenarios and likelihood · Policy repository / GRC workspace
Approval and review dates of the BIA and risk assessment · Policy repository / GRC workspace
Records of BIA updates following new services or major changes · Document repository

governing documentDocuments that govern the control

Criteria for continuity strategies derived from the BIA (for example maximum tolerable downtime) · Document repository

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

BIA performed once and never refreshed
Recovery objectives set by IT without business owner input
New cloud services launched with no impact analysis

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

BCR-01 Business Continuity Management Policy and Procedures · BCR-03 Business Continuity Strategy