ID.RA-05 Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization
Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization.
5
artefacts
1
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
- Risk heat map and prioritization output · Document repository
periodic reviewEvidence produced at each review
- Annual register attestation · Vendor register / contract repository
governing documentDocuments that govern the control
- Inherent risk register with scoring rationale · Policy repository / GRC workspace
- Linkage from inherent to residual risk · Document repository
- Methodology document shared across teams · Document repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Document repository on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Inherent risk inflated to justify spending
- Heat map static between reviews
- Residual calculation opaque
- Methodology applied inconsistently
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-04 Potential impacts and likelihoods of threats exploiting vulnerabilities are identified and recorded · ID.RA-06 Risk responses are chosen, prioritized, planned, tracked, and communicated