8.2 Business impact analysis and risk assessment
Run and maintain the processes that establish what disruption would cost the organization over time and what could cause it, and refresh both whenever the organization or its operating context changes significantly.
Source: ISO 22301:2019, 8.2. 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 ISO 22301:2019 in the compliance library.
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
- Current outputs of both · Document repository
periodic reviewEvidence produced at each review
- Review triggers and evidence of review after significant change · Document repository
governing documentDocuments that govern the control
- Documented BIA and risk assessment processes · Policy repository / GRC workspace
First move
Common gaps auditors find
- Both performed once at implementation and treated as permanent
- No defined trigger for refresh, so significant change passes unnoticed
- Risk assessment run without reference to the BIA outputs it should be scoped by
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