# NIST SP 800-53 Rev. 5 RA-5(5) — Privileged Access - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ra-5-5-privileged-access - Section: [Compliance](https://support.icompaas.com/compliance) › [NIST SP 800-53 Rev. 5 Controls](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5) › RA — Risk Assessment - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-53 Rev. 5**·Control `RA-5(5)`·medium·Component: **Risk Assessment** ## What this control requires > Authorize privileged access to specific system components for vulnerability scanning that may involve sensitive or intrusive activities, ensuring both depth of assessment and protection of sensitive data. This control supports the Privileged Scan Gateway capability within the Risk Assessment family. > > — NIST SP 800-53 Rev. 5, Control RA-5(5) ### In plain English Authorize privileged access to specific system components for vulnerability scanning that may involve sensitive or intrusive activities, ensuring both depth of assessment and protection of sensitive data. 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. ## 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(5)) 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. - **Data.** Document the trigger, the owner and the cadence. - **Authorize.** Document the trigger, the owner and the cadence. - **Review.** Document the trigger, the owner and the cadence. - **Protection.** Document the trigger, the owner and the cadence. - **Scope:** management, system, protection, identity, assessment, review, components, capability. ## 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: Privileged Access. ## 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 14.9** — Conduct Role-Specific Security Awareness and Skills Training](https://support.icompaas.com/compliance/cis-controls-v8/14-9-conduct-role-specific-security-awareness-and-skills-training) - [**NIST SP 800-171 Rev. 3 3.15.2** — System Security Plan](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-15-2-system-security-plan) - [**SOC 2 (2017 TSC) CC6.2** — Access Provisioning](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc6-2-access-provisioning) - [**ISO/IEC 27001:2022 A.8.2** — Privileged access rights](https://support.icompaas.com/compliance/iso-27001-2022/a-8-2-privileged-access-rights) - [**BSI C5:2020 PSS-03** — Online Register of Known Vulnerabilities](https://support.icompaas.com/compliance/bsi-c5-2020/pss-03-online-register-of-known-vulnerabilities) ## Related controls in NIST SP 800-53 Rev. 5 - [**Control RA-9** — Criticality Analysis](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ra-9-criticality-analysis) - [**Control SC-2(1)** — Interfaces For Non-Privileged Users](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sc-2-1-interfaces-for-non-privileged-users) - [**Control RA-3** — Risk Assessment](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ra-3-risk-assessment) - [**Control AC-6(6)** — Privileged Access By Non-Organizational Users](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-6-6-privileged-access-by-non-organizational-users) - [**Control CM-5(4)** — Dual Authorization](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cm-5-4-dual-authorization) - [**Control IA-4** — Identifier Management](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ia-4-identifier-management) ## References - [NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5](https://csrc.nist.gov/Projects/risk-management/sp800-53-controls) - Catalogue identifier: `Control RA-5(5)` Topics: identity accessprivileged accessidentity managementvulnerability managementaccess review ## Related compliance guidance - [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): Start with the full NIST SP 800-53 implementation guide — scope, roadmap, evidence and how the assessment runs. - [NIST SP 800-171 and CMMC: a practical guide to protecting CUI in the cloud](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3): If your obligation is protecting CUI in your own systems for a federal or defence contract, this derived subset — not the full catalogue — is the requirement. - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Most commercial SaaS already hold a SOC 2 Type 2, and FedRAMP 20x Class A is designed for providers that have one.