Risk register
24 risks · last review 12 September
Acceptance of residual risk RSK-012 awaiting the management body
Platform · Risk management
NIS2 (art. 21.2(a)) and ISO/IEC 27001 require a risk analysis that drives the choice of measures; DORA (art. 5) makes the management body responsible for ICT risk. In EVIDEVO each risk has likelihood and impact on a shared scale, an owner, a treatment plan and the controls that reduce it, with their test outcomes. Residual risk is accepted through a recorded approval.
Data for illustrative purposes only, not real
The problem
A document written for the audit and then filed away, which does not follow changes to systems and vendors.
There is no record of which control reduces which risk, or whether that control works.
Residual risks are accepted verbally, with no date and no signatory.
What it does
Threats, assets involved, likelihood and impact, on a shared scale.
Each risk shows the controls that reduce it and their test outcomes.
Actions with owner and deadline, tracked to closure.
Residual risk is accepted through a recorded approval: who, when, at what risk level.
Review reminders and comparison with the previous assessment.
Top risks and trend, in the format of the management body reports.
The outcome
Other capabilities
It starts from the frameworks in scope and how the work is organised today. In thirty minutes, EVIDEVO is shown working in that context.