ID.RA-04 Potential impacts and likelihoods of threats exploiting vulnerabilities are identified and recorded
Potential impacts and likelihoods of threats exploiting vulnerabilities are identified and recorded.
5
artefacts
0
held by a system
0
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
none for this control
governing documentDocuments that govern the control
- Risk scenario library with impact and likelihood scores · Document repository
- Scenario simulation outputs and decisions · Document repository
- Quantitative loss exposure analyses where applicable · Document repository
- Cross functional risk workshop notes · Document repository
- Validation of scenarios by independent reviewers · 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
- Scenarios limited to known historical events
- Likelihoods estimated without calibration
- Workshops dominated by single perspective
- Validation skipped
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 sheetID.RA-03 Internal and external threats to the organization are identified and recorded · ID.RA-05 Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization