6.1 Actions to address risks and opportunities
Work out what could help or hinder the management system itself and plan what to do about it, keeping this separate from the disruption risks handled under business impact analysis and risk assessment.
3
artefacts
0
held by a system
1
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
- Evidence that BCMS risk is kept distinct from operational disruption risk · Document repository
governing documentDocuments that govern the control
- Register of risks and opportunities relating to BCMS effectiveness · Policy repository / GRC workspace
- Planned actions with owners and integration points into BCMS processes · 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
- BCMS risk conflated with disruption risk, so management system weaknesses are never surfaced
- Opportunities omitted entirely, leaving a one sided risk register
- Actions planned but never integrated into a BCMS process or evaluated
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 sheet5.3 Roles, responsibilities and authorities · 6.1.1 Determining risks and opportunities