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.
3
artefacts
0
held by a system
2
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
- Documented BIA and risk assessment processes · Policy repository / GRC workspace
- Review triggers and evidence of review after significant change · Document repository
governing documentDocuments that govern the control
- Current outputs of both · 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
- 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