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

4
artefacts
0
held by a system
0
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Business impact analysis methodology document · Document repository
  • Completed analysis listing critical products and services with their dependencies · 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

This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.

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