What evidence do auditors commonly ask for on ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded?

Vulnerability scanning coverage report; Vulnerability triage workflow with severity SLAs; Validated findings with proof and remediation status; Asset coverage exceptions register; Trend analysis on vulnerability backlog.

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

Coverage gaps for cloud and container workloads

NIST CSF 2.0 · ID - Identify

`ID.RA-01` Vulnerabilities in assets are identified, validated, and recorded

Vulnerabilities in assets are identified, validated, and recorded. Control from NIST Cybersecurity Framework 2.0 framework, domain: ID - Identify.

Source: NIST CSF 2.0, ID.RA-01. 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

Vulnerability scanner / patch tooling

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

Vulnerability scanning coverage report · Vulnerability scanner / patch tooling

periodic reviewEvidence produced at each review

Validated findings with proof and remediation status · Document repository
Trend analysis on vulnerability backlog · Vulnerability scanner / patch tooling

governing documentDocuments that govern the control

Vulnerability triage workflow with severity SLAs · Policy repository / GRC workspace
Asset coverage exceptions register · Policy repository / GRC workspace

First move

Mostly documents and reviews. Pull the 1 system-held artefact from your Vulnerability scanner / patch tooling 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

Coverage gaps for cloud and container workloads
SLAs missed for high severity items
Findings closed without re scan
Trend backlog growing over time

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.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated… · ID.RA-02 Cyber threat intelligence is received from information sharing forums and sources