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.

Related controls in NIST SP 800-53 Rev. 5

References

Topics: governance riskvendor riskvendor managementsupply chain securitythird party monitoring