What is the most common gap auditors find on ID.RA-04?

Scenarios limited to known historical events

`ID.RA-04` Potential impacts and likelihoods of threats exploiting vulnerabilities are identified and recorded

Q: What evidence do auditors commonly ask for on ID.RA-04 Potential impacts and likelihoods of threats exploiting vulnerabilities are identified and recorded?

Risk scenario library with impact and likelihood scores; Scenario simulation outputs and decisions; Quantitative loss exposure analyses where applicable; Cross functional risk workshop notes; Validation of scenarios by independent reviewers.

Potential impacts and likelihoods of threats exploiting vulnerabilities are identified and recorded

Source: NIST CSF 2.0, ID.RA-04. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open NIST CSF 2.0 in the compliance library.

artefacts

held by a system

at each review

hard

to go live

Document repository

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

Scenario simulation outputs and decisions · Document repository
Quantitative loss exposure analyses where applicable · Document repository
Cross functional risk workshop notes · Document repository

governing documentDocuments that govern the control

Risk scenario library with impact and likelihood scores · Document repository
Validation of scenarios by independent reviewers · Document repository

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

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 sheet

ID.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…