NIST SP 800-53 Rev. 5 SR-5 — Acquisition Strategies, Tools, And Methods

What this control requires

Implement acquisition strategies, contract tools, and procurement methods to protect against, identify, and mitigate supply chain risks. Techniques may include obscuring system end-use, using tamper-evident packaging, blind buys, and requiring controlled distribution. The goal is to protect against unauthorized production, tampering, counterfeit insertion, and malicious software during the system development lifecycle. This control supports the Acquisition Strategies, Contract Management, Supply Chain Security capability within the Supply Chain Risk Management family.

In plain English

Implement acquisition strategies, contract tools, and procurement methods to protect against, identify, and mitigate supply chain risks. 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 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) and look for objective evidence on the latest two assessment cycles.

How to implement

Secure Development

Pipeline. Require code review, SAST (Semgrep / Snyk Code), SCA (Dependabot / Renovate), secret-scanning and IaC scanning in the merge pipeline.

Branch protection. Protected branches enforce reviews, signed commits and passing CI before merge; document the protection rules as the control evidence.

Operational checklist

• Access. Document the trigger, the owner and the cadence.
• Security. Document the trigger, the owner and the cadence.
• Review. Document the trigger, the owner and the cadence.
• Chain. Document the trigger, the owner and the cadence.
• Unauthorized. Document the trigger, the owner and the cadence.
• Scope: management, system, identity, software, review, capability, tools, techniques.

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: Acquisition Strategies, Tools, And Methods.

Common pitfalls

• CI security checks set to warn-only; the merge button is faster than the security feedback.

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.8.4 — Access to source code
• NIST SP 800-171 Rev. 3 3.4.10 — System Component Inventory

Related controls in NIST SP 800-53 Rev. 5

• Control SR-11(1) — Anti-Counterfeit Training
• Control PM-7 — Enterprise Architecture
• Control SA-15(5) — Attack Surface Reduction
• Control SI-7(15) — Code Authentication
• Control SA-3 — System Development Life Cycle
• Control AC-6(3) — Network Access To Privileged Commands

References

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

Topics: governance riskidentity managementaccess reviewprivileged accesssecure development