# NIST SP 800-53 Rev. 5 SR-5(1) — Adequate Supply - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sr-5-1-adequate-supply - 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) › SR — Supply Chain Risk Management - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-53 Rev. 5**·Control `SR-5(1)`·high·Component: **Supply Chain Risk Management** ## What this control requires > Implement controls to ensure the availability of critical system components. These may include using multiple suppliers, stockpiling spare parts, and identifying functionally identical components. Tracking component mean time to failure helps mitigate risks from disruptions or failures in the supply chain. This control supports the Acquisition Strategy, Supply Chain Continuity capability within the Supply Chain Risk Management family. > > — NIST SP 800-53 Rev. 5, Control SR-5(1) ### In plain English Implement controls to ensure the availability of critical system components. In practice, this means you can prove you security 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 **Supply Chain Risk Management**, the assessor will trace your implementation back to the catalogue reference (Control SR-5(1)) and look for objective evidence on the latest two assessment cycles. ## How to implement 1. Write a short policy stating intent, scope and named owner. 2. Encode it as a platform guardrail — SCP, Azure Policy initiative, Organisation Policy, or repository policy. 3. Wire a monitoring signal that catches drift (CSPM rule, SIEM rule, scheduled query, Workspace alert) and ticket it. 4. Review on a documented cadence and capture the review in the risk register or compliance tracker. ### Operational checklist - **Security.** Document the trigger, the owner and the cadence. - **Time.** Document the trigger, the owner and the cadence. - **Chain.** 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. - **Scope:** management, system, mitigate risks, controls, time, failure, components, capability. ## Evidence to collect - **Vendor Risk Management.** `vendor_risk_management` evidence Third-party risk management evidence (assessments, contracts, due diligence) shows supplier oversight. Focus: Adequate Supply. ## 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.16.2** — Unsupported System Components](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-16-2-unsupported-system-components) - [**ISO/IEC 27001:2022 A.5.19** — Information security in supplier relationships](https://support.icompaas.com/compliance/iso-27001-2022/a-5-19-information-security-in-supplier-relationships) - [**ISO/IEC 42001:2023 A.10.3** — Suppliers](https://support.icompaas.com/compliance/iso-42001-2023/a-10-3-suppliers) ## Related controls in NIST SP 800-53 Rev. 5 - [**Control SR-3(1)** — Diverse Supply Base](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sr-3-1-diverse-supply-base) - [**Control SA-22** — Unsupported System Components](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-22-unsupported-system-components) - [**Control SR-3(3)** — Sub-Tier Flow Down](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sr-3-3-sub-tier-flow-down) - [**Control SA-12(2)** — Supplier Reviews](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-12-2-supplier-reviews) - [**Control SR-6** — Supplier Assessments And Reviews](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sr-6-supplier-assessments-and-reviews) - [**Control SA-12(6)** — Minimizing Procurement Time](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-12-6-minimizing-procurement-time) ## 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 SR-5(1)` Topics: governance riskvendor riskvendor managementsupply chain securitythird party monitoring ## 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.