NIST SP 800-53 Rev. 5 RA-5(2) — Update Vulnerabilities To Be Scanned : iCompaas Support

NIST SP 800-53 Rev. 5·Control RA-5(2)·high·Component: Risk Assessment

What this control requires

Regularly update the set of system vulnerabilities to be scanned, including prior to scans or upon identification of new issues, ensuring prompt mitigation of emerging risks. This control supports the Vulnerability Update Scheduler capability within the Risk Assessment family.
— NIST SP 800-53 Rev. 5, Control RA-5(2)

In plain English

Regularly update the set of system vulnerabilities to be scanned, including prior to scans or upon identification of new issues, ensuring prompt mitigation of emerging risks. In practice, this means you can prove you policy management-level controls on a defined cadence.

Why it matters

SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed.

This control is rated high. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

What an auditor looks for

A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan.

Within Risk Assessment, the assessor will trace your implementation back to the catalogue reference (Control RA-5(2)) and look for objective evidence on the latest two assessment cycles.

How to implement

Policy Management

Docs. Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.

Vulnerability Management

Scanners. Pair an unauthenticated scanner (Nessus / Qualys / Tenable.io) for external surface with an authenticated agent for OS/library CVEs on every host.

SLA. Document remediation SLAs by CVSS / EPSS: critical 7 days, high 30 days, medium 90 days; report monthly trend to leadership.

Containers. Scan images in CI (Trivy / Grype / Snyk Container) AND at runtime; block deploys on critical findings without exception.

Operational checklist

Policy. Document the trigger, the owner and the cadence.
System. Document the trigger, the owner and the cadence.
Control. Document the trigger, the owner and the cadence.
Identification. Document the trigger, the owner and the cadence.
Vulnerability. Document the trigger, the owner and the cadence.
Scope: management, system, assessment, capability, identification, policy, vulnerability.

Evidence to collect

Policy Document. A signed and version-controlled policy / standard / procedure document.

Signed policy or standard documents the safeguard. Focus: Update Vulnerabilities To Be Scanned.

Common pitfalls

Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.
Scans that hit only the perimeter; missing authenticated scans of OS, runtime libs and base images so most CVEs are invisible.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

Related controls in NIST SP 800-53 Rev. 5

References

NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5
Catalogue identifier: Control RA-5(2)

Topics: governance riskpatch managementpolicy managementvulnerability management

NIST SP 800-53 Rev. 5 RA-5(2) — Update Vulnerabilities To Be Scanned