8.2.3 Risk assessment
Implement and maintain a risk assessment process that identifies the risks of disruption to the organization's prioritized activities and the resources they require, analyses and evaluates those risks, and determines whi
4
artefacts
0
held by a system
2
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
- Documented risk assessment process · Policy repository / GRC workspace
- Analysis and evaluation records with the criteria applied · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Risk register scoped to prioritized activities and their required resources · Policy repository / GRC workspace
- Treatment decisions recorded with rationale, including acceptance · 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
- Risk register covering the enterprise generally rather than the prioritized activities specifically
- Evaluation criteria undefined, so treatment decisions are unreviewable
- Resource level risks such as single site or single supplier concentration not surfaced
- Accepted risks recorded without an acceptance authority
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.2 Business impact analysis · 8.3 Business continuity strategies and solutions