8.2.1 General
Implement and maintain systematic processes for analysing the business impact of disruption and for assessing disruption risk, and review the outputs of both at planned intervals and whenever there is significant change
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
- Planned review interval with evidence reviews occurred · Document repository
- Change triggered reviews evidenced against actual organizational changes · Document repository
governing documentDocuments that govern the control
- Written method for each process showing it is systematic and repeatable · 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
- Method exists as a spreadsheet convention rather than a documented process
- Planned interval set at annual and then missed without escalation
- Significant change defined nowhere, so the change trigger never fires
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 sheet8.2 Business impact analysis and risk assessment · 8.2.2 Business impact analysis