NIST SP 800-53 Rev. 5 RA-5(3) — Breadth And Depth Of Coverage

What this control requires

Define how extensively and deeply vulnerability scans are performed--across system components and within system layers--to match organizational risk tolerance and ensure comprehensive coverage. This control supports the Coverage Configuration Profile capability within the Risk Assessment family.

In plain English

Define how extensively and deeply vulnerability scans are performed--across system components and within system layers--to match organizational risk tolerance and ensure comprehensive coverage. In practice, this means you can prove you configuration 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(3)) and look for objective evidence on the latest two assessment cycles.

How to implement

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.

Code Review Testing

Pipeline. Require at least one human reviewer plus passing CI (lint, type, unit, security scan) before merge — protected branches enforce this.

Operational checklist

• Configuration. Document the trigger, the owner and the cadence.
• Review. 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.
• Testing,. Document the trigger, the owner and the cadence.
• Scope: management, system, assessment, configuration, review, components, capability, system components.

Evidence to collect

• Vapt Scan. vapt_scan evidence

Pen-test and vulnerability scan reports substantiate attack-surface coverage. Focus: Breadth And Depth Of Coverage.

Common pitfalls

• 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.

• NIST SP 800-171 Rev. 3 3.11.2 — Vulnerability Monitoring and Scanning

Related controls in NIST SP 800-53 Rev. 5

• Control RA-5(10) — Correlate Scanning Information
• Control CA-8(1) — Independent Penetration Testing Agent Or Team
• Control CA-8 — Penetration Testing
• Control RA-5(9) — Penetration Testing And Analyses
• Control SA-11(5) — Penetration Testing
• Control RA-5(1) — Update Tool Capability

References

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

Topics: governance riskvulnerability managementcode review testing