6.1.1 Determining risks and opportunities
Taking the context issues and interested party requirements already identified, determine which risks and opportunities must be addressed so the BCMS achieves its intended outcomes, prevents or reduces undesired effects,
3
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
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
- Review record showing the register is maintained · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Risk and opportunity register traceable to specific context issues and party requirements · Policy repository / GRC workspace
- Statement of the intended BCMS outcomes the register is judged against · Policy repository / GRC workspace
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
- Register produced independently of the context analysis, so the two never agree
- Only threats recorded, with continual improvement opportunities absent
- No stated BCMS outcome, so nothing anchors what counts as a risk
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 sheet6.1 Actions to address risks and opportunities · 6.1.2 Addressing risks and opportunities