NIST 800-53 REV 5 • SUPPLY CHAIN RISK MANAGEMENT

SR-5Acquisition Strategies, Tools, and Methods

Employ the following acquisition strategies, contract tools, and procurement methods to protect against, identify, and mitigate supply chain risks: {{ insert: param, sr-05_odp }}.

CMMC Practice Mapping

No direct CMMC mapping

NIST 800-171 Mapping

No direct NIST 800-171 mapping

Supplemental Guidance

The use of the acquisition process provides an important vehicle to protect the supply chain. There are many useful tools and techniques available, including obscuring the end use of a system or system component, using blind or filtered buys, requiring tamper-evident packaging, or using trusted or controlled distribution. The results from a supply chain risk assessment can guide and inform the strategies, tools, and methods that are most applicable to the situation. Tools and techniques may provide protections against unauthorized production, theft, tampering, insertion of counterfeits, insertion of malicious software or backdoors, and poor development practices throughout the system development life cycle. Organizations also consider providing incentives for suppliers who implement controls, promote transparency into their processes and security and privacy practices, provide contract language that addresses the prohibition of tainted or counterfeit components, and restrict purchases from untrustworthy suppliers. Organizations consider providing training, education, and awareness programs for personnel regarding supply chain risk, available mitigation strategies, and when the programs should be employed. Methods for reviewing and protecting development plans, documentation, and evidence are commensurate with the security and privacy requirements of the organization. Contracts may specify documentation protection requirements.

Practitioner Notes

Use acquisition strategies, tools, and methods that reduce supply chain risk — build security into your procurement process from the beginning.

Example 1: Include security requirements in all RFPs and procurement documents. Require vendors to demonstrate FIPS 140-2 validated encryption, SOC 2 Type II reports, and vulnerability management programs. Make these requirements mandatory, not optional.

Example 2: Use the GSA IT Schedule or other vetted procurement vehicles for IT purchases. These channels provide some assurance that vendors have been reviewed. For software, prefer products on the DoD's approved products list or FedRAMP-authorized cloud services.