EvidenceSheet

BCM-02 Business impact analysis policies and instructions

Document, communicate and provide business impact analysis rules covering risk based scenarios, critical products and services, dependencies, threats, effects of planned and unplanned outages over time, maximum tolerable outage, restoration priorities, recovery time and data loss targets, and resources needed to resume.

Source: BSI C5 (121-criteria catalogue), BCM-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 BSI C5 (121-criteria catalogue) in the compliance library.

The edition of the catalogue is not stamped here; check the edition your attestation is issued against.

4
artefacts
0
held by a system
1
at each review
hard
to go live
Document repository
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

  • Completed analysis listing critical products and services with their dependencies · Document repository

governing documentDocuments that govern the control

  • Business impact analysis methodology document · Document repository
  • Recorded recovery time and recovery point objectives per critical service · Policy repository / GRC workspace
  • Threat and scenario catalogue used as input to the analysis · 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

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

BCM-01 Top management responsibility · BCM-03 Planning business continuity