NIST SP 800-53 Rev. 5 SR-3(2) — Limitation Of Harm

What this control requires

Implement controls to minimize harm from adversaries targeting the supply chain by avoiding custom configurations, using reputable vendors, adhering to Maintenance schedules, and maintaining contingency plans. These measures reduce the probability of supply chain attacks. This control supports the Procurement, Vendor Management, Incident Response capability within the Supply Chain Risk Management family.

In plain English

Implement controls to minimize harm from adversaries targeting the supply chain by avoiding custom configurations, using reputable vendors, adhering to Maintenance schedules, and maintaining contingency plans. 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-3(2)) 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.
• Maintenance. Document the trigger, the owner and the cadence.
• Response. Document the trigger, the owner and the cadence.
• Chain. Document the trigger, the owner and the cadence.
• Control. Document the trigger, the owner and the cadence.
• Scope: management, controls, maintenance, capability, incident response capability, implement, security, harm.

Evidence to collect

• Vendor Risk Management. vendor_risk_management evidence

Third-party risk management evidence (assessments, contracts, due diligence) shows supplier oversight. Focus: Limitation Of Harm.

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.

• ISO/IEC 27001:2022 A.5.20 — Addressing information security within supplier agreements
• SOC 2 (2017 TSC) CC9.2 — Vendor Risk Management
• BSI C5:2020 OIS-03 — Interfaces and Dependencies
• NIST SP 800-171 Rev. 3 3.16.2 — Unsupported System Components

Related controls in NIST SP 800-53 Rev. 5

• Control SR-3(3) — Sub-Tier Flow Down
• Control SR-3(1) — Diverse Supply Base
• Control SR-3 — Supply Chain Controls And Processes
• Control SR-5(1) — Adequate Supply
• Control SA-12(2) — Supplier Reviews
• Control SA-22 — Unsupported System Components

References

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

Topics: vendor riskvendor managementsupply chain securitythird party monitoring