8.2.2 Business impact analysis
Use the impact analysis process to set continuity priorities and requirements: define the impact types and criteria relevant to the organization's context, identify the activities supporting delivery of products and serv
5
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
- Defined impact types and criteria approved for this organization · Document repository
- Activity inventory mapped to products and services · Policy repository / GRC workspace
- Impact over time analysis per activity · Document repository
- Maximum tolerable period of disruption and resumption time frames with minimum acceptable capacity, approved by management · Policy repository / GRC workspace
- Prioritized activity list with resource, dependency and interdependency mapping · 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
- Recovery time frames set by aspiration and never reconciled to the impact analysis that should produce them
- Minimum acceptable capacity omitted, so a plan can claim recovery at any level of service
- Dependencies mapped one level deep, missing the supplier behind the supplier
- Impact criteria copied from a template rather than defined for this organization's context
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