← NIST CSF 2.0 · IDENTIFY — Risk Assessment
ID.RA-01 — Vulnerabilities are identified, validated and recorded
critical
vulnerability-management
Requirement
Vulnerabilities in assets are identified, validated and recorded.
What the engine looks for
Every group below must be satisfied — by an affirmative statement, not a plan, a hedge or a denial — for the control to count as covered. A term ending in … matches any word it begins. Supporting terms do not change the verdict — they raise confidence and distinguish a policy that names a mechanism from one that gestures at a category.
Required element 1 — any one of
vulnerability
Required element 2 — any one of
scanidentif…assessrecordtrack
Supporting terms — specificity signals
cvecvssauthenticated scanscapenetration testbug bountybacklog
Contradiction markers
Finding any of these outranks coverage — a policy that admits the gap is worse than silence.
no vulnerability scanning
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| PCI DSS 4.0.1 | 11.3 | Internal and external vulnerability scanning every three months | vulnerability-management |
| SOC 2 | CC7.1 | Detection of configuration changes and vulnerabilities | vulnerability-management |
| ISO 27001 | A.5.7 | Threat intelligence | vulnerability-management |
| ISO 27001 | A.8.8 | Management of technical vulnerabilities | vulnerability-management |
| PCI DSS 4.0.1 | 6.3.3 | Security patches installed within defined timeframes | vulnerability-management |
| GLBA | 314.4(d) | Continuous monitoring, or annual penetration tests and six-monthly vulnerability assessments | vulnerability-management |