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.
5
artefacts
0
held by a system
0
at each review
hard
to go live
Policy repository / GRC workspace
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
- Vulnerability scanning coverage report · Policy repository / GRC workspace
- Vulnerability triage workflow with severity SLAs · Policy repository / GRC workspace
- Validated findings with proof and remediation status · Document repository
- Asset coverage exceptions register · Policy repository / GRC workspace
- Trend analysis on vulnerability backlog · Policy repository / GRC workspace
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
- 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 sheetID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved · ID.RA-02 Cyber threat intelligence is received from information sharing forums and sources