6.1.2 Addressing risks and opportunities
Plan the actions that will address those risks and opportunities, and plan how each action will be integrated into and implemented within BCMS processes and how its effectiveness will subsequently be evaluated.
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 of implementation within that process · Document repository
governing documentDocuments that govern the control
- Action plan naming owner, target date and the BCMS process the action lands in · Policy repository / GRC workspace
- Effectiveness evaluation carried out through performance evaluation · 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
- Actions closed on completion with no evaluation of whether they worked
- Actions held in a standalone tracker that never touches a BCMS process
- No effectiveness criterion set, so evaluation has nothing to test against
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.1 Determining risks and opportunities · 6.2 Business continuity objectives and planning to achieve them