NIST SP 800-53 Rev. 5 RA-3 — Risk Assessment

What this control requires

Conduct regular risk assessments to identify threats, vulnerabilities, and impacts on systems and individuals. Evaluate likelihood and severity of harm, document results, share findings with relevant roles, and update when conditions change. This control supports the Risk Management Engine capability within the Risk Assessment family.

In plain English

Conduct regular risk assessments to identify threats, vulnerabilities, and impacts on systems and individuals. In practice, this means you can prove you access 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 critical in the source catalogue. Treat gaps here as production incidents in the risk register, not housekeeping.

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

Operational checklist

• Access. Document the trigger, the owner and the cadence.
• Review. Document the trigger, the owner and the cadence.
• Identity. Document the trigger, the owner and the cadence.
• Control. Document the trigger, the owner and the cadence.
• Identify. Document the trigger, the owner and the cadence.
• Scope: management, conditions, identity, assessments, assessment, review, capability, threats.

Evidence to collect

• Identity Scan. IAM / IdP exports — Entra ID, Okta, IAM Identity Center, Workspace directory — showing accounts, roles, MFA state and last sign-in.

Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Focus: Risk Assessment.

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.

• CIS Controls v8 6.1 — Establish an Access Granting Process
• ISO/IEC 27001:2022 A.5.16 — Identity management
• NIST SP 800-171 Rev. 3 3.1.22 — Publicly Accessible Content
• BSI C5:2020 PSS-03 — Online Register of Known Vulnerabilities
• ISO/IEC 27701:2025 A.3.8 — Identity management

Related controls in NIST SP 800-53 Rev. 5

• Control RA-5(5) — Privileged Access
• Control CA-3(6) — Transfer Authorizations
• Control CA-6 — Authorization
• Control IR-9 — Information Spillage Response
• Control SC-42(1) — Reporting To Authorized Individuals Or Roles
• Control MP-6(8) — Remote Purging Or Wiping Of Information

References

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

Topics: governance riskidentity accessidentity managementaccess reviewprivileged accessvulnerability management