Knowledge is Power

Sitewide Search

Search Bare Metal Cyber

Search courses, individual lessons, wiki entries, books, podcasts, magazine articles, Daily Cyber News, and Darwin.

NIST SP 800-53 Learning Center

SR-5 — Acquisition Strategies, Tools, and Methods

Read the official control and assessment content, then use the separately labeled Bare Metal Cyber perspective to connect the requirement to implementation, evidence, and sustained operation.

2Enhancements
1Parameters
3Baseline memberships
3Assessment methods

SR — Supply Chain Risk Management · NIST SP 800-53 Release 5.2.0

LowModerateHigh
Official NIST control content

Control statement

Employ the following acquisition strategies, contract tools, and procurement methods to protect against, identify, and mitigate supply chain risks: [Organization-defined: strategies, tools, and methods].

Official NIST discussion

Discussion

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.

Official OSCAL parameters

Organization-defined parameters

These values must be resolved through the organization’s tailoring and governance process. Bracketed parameter references in the control text identify where a decision is required.

strategies, tools, and methodsacquisition strategies, contract tools, and procurement methods to protect against, identify, and mitigate supply chain risks are defined;
Original Bare Metal Cyber perspective

From control text to operational evidence

Use Acquisition Strategies, Tools, and Methods as a testable risk decision. Translate the official statement into accountable people, repeatable processes, configured technology, and evidence that demonstrates the outcome over time. In this family, pay particular attention to cybersecurity supply-chain governance, provenance, supplier risk, component authenticity, and dependency resilience.

Implementation workflow

  • Define the control boundary, responsible owner, inherited portions, and systems or processes in scope.
  • Resolve each organization-defined parameter before declaring the control implemented.
  • Document how the implementation satisfies every clause of the official control statement.
  • Collect evidence as a normal byproduct of operation rather than only before an assessment.
  • Review exceptions, changes, and monitoring results on a risk-based cadence.

Evidence examples

  • supplier inventories and criticality ratings
  • contract security clauses
  • provenance and authenticity records
  • supplier monitoring and incident records

Common failure patterns

  • tier-one vendors assessed while sub-tier dependencies are ignored
  • contracts lack evidence and notification obligations
  • open-source and service dependencies omitted
  • supplier risk reviews occur only at onboarding

Questions practitioners should ask

  • What risk decision is this control intended to support in this system?
  • Which parts are implemented locally, inherited, shared, or not applicable—and what evidence supports that decision?
  • Do the documented narrative, deployed configuration, operating process, and collected evidence agree?
  • What event or threshold requires the implementation to be reviewed or changed?
Official NIST SP 800-53A content

Assessment objectives and methods

Show the assessment objective
  1. SR-05[01][Organization-defined: strategies, tools, and methods] are employed to protect against supply chain risks;
  2. SR-05[02][Organization-defined: strategies, tools, and methods] are employed to identify supply chain risks;
  3. SR-05[03][Organization-defined: strategies, tools, and methods] are employed to mitigate supply chain risks.

Examine

  • Supply chain risk management policy
  • supply chain risk management procedures
  • supply chain risk management plan
  • system and services acquisition policy
  • system and services acquisition procedures
  • procedures addressing supply chain protection
  • procedures addressing the integration of information security and privacy requirements into the acquisition process
  • solicitation documentation
  • acquisition documentation (including purchase orders)
  • service level agreements
  • acquisition contracts for systems, system components, or services
  • documentation of training, education, and awareness programs for personnel regarding supply chain risk
  • system security plan
  • privacy plan
  • other relevant documents or records

Interview

  • Organizational personnel with acquisition responsibilities
  • organizational personnel with information security and privacy responsibilities
  • organizational personnel with supply chain risk management responsibilities

Test

  • Organizational processes for defining and employing tailored acquisition strategies, contract tools, and procurement methods
  • mechanisms supporting and/or implementing the definition and employment of tailored acquisition strategies, contract tools, and procurement methods
Official relationships

Related controls

These relationships come from the official OSCAL catalog. They indicate useful dependencies or context, not automatic inheritance or equivalence.

Official NIST enhancements

Control enhancements

Enhancements add specificity, strength, or scope to the base control. Baseline badges show explicit selections in the official SP 800-53B OSCAL profiles.

Official NIST control enhancement

SR-5(1) — Adequate Supply

Employ the following controls to ensure an adequate supply of [Organization-defined: critical system components]: [Organization-defined: controls].

Official discussion

Adversaries can attempt to impede organizational operations by disrupting the supply of critical system components or corrupting supplier operations. Organizations may track systems and component mean time to failure to mitigate the loss of temporary or permanent system function. Controls to ensure that adequate supplies of critical system components include the use of multiple suppliers throughout the supply chain for the identified critical components, stockpiling spare components to ensure operation during mission-critical times, and the identification of functionally identical or similar components that may be used, if necessary.

Organization-defined parameters (2)
controlscontrols to ensure an adequate supply of critical system components are defined;
critical system componentscritical system components of which an adequate supply is required are defined;
Assessment objectives and methods

[Organization-defined: controls] are employed to ensure an adequate supply of [Organization-defined: critical system components].

Examine

  • Supply chain risk management policy and procedures
  • supply chain risk management strategy
  • supply chain risk management plan
  • contingency planning documents
  • inventory of critical systems and system components
  • determination of adequate supply
  • system and services acquisition policy
  • procedures addressing supply chain protection
  • procedures addressing the integration of information security requirements into the acquisition process
  • procedures addressing the integration of acquisition strategies, contract tools, and procurement methods into the acquisition process
  • solicitation documentation
  • acquisition documentation
  • service level agreements
  • acquisition contracts for systems or services
  • purchase orders/requisitions for the system, system component, or system service from suppliers
  • system security plan
  • other relevant documents or records

Interview

  • Organizational personnel with system and services acquisition responsibilities
  • organizational personnel with information security responsibilities
  • organizational personnel with supply chain risk management responsibilities

Test

  • Organizational processes for defining and employing tailored acquisition strategies, contract tools, and procurement methods
  • mechanisms supporting and/or implementing the definition and employment of tailored acquisition strategies, contract tools, and procurement methods
Related controls
Official NIST control enhancement

SR-5(2) — Assessments Prior to Selection, Acceptance, Modification, or Update

Assess the system, system component, or system service prior to selection, acceptance, modification, or update.

Official discussion

Organizational personnel or independent, external entities conduct assessments of systems, components, products, tools, and services to uncover evidence of tampering, unintentional and intentional vulnerabilities, or evidence of non-compliance with supply chain controls. These include malicious code, malicious processes, defective software, backdoors, and counterfeits. Assessments can include evaluations; design proposal reviews; visual or physical inspection; static and dynamic analyses; visual, x-ray, or magnetic particle inspections; simulations; white, gray, or black box testing; fuzz testing; stress testing; and penetration testing (see [SR-6(1)](#sr-6.1) ). Evidence generated during assessments is documented for follow-on actions by organizations. The evidence generated during the organizational or independent assessments of supply chain elements may be used to improve supply chain processes and inform the supply chain risk management process. The evidence can be leveraged in follow-on assessments. Evidence and other documentation may be shared in accordance with organizational agreements.

Assessment objectives and methods
  1. SR-05(02)[01]the system, system component, or system service is assessed prior to selection;
  2. SR-05(02)[02]the system, system component, or system service is assessed prior to acceptance;
  3. SR-05(02)[03]the system, system component, or system service is assessed prior to modification;
  4. SR-05(02)[04]the system, system component, or system service is assessed prior to update.

Examine

  • System security plan
  • system and services acquisition policy
  • procedures addressing supply chain protection
  • procedures addressing the integration of information security requirements into the acquisition process
  • security test and evaluation results
  • vulnerability assessment results
  • penetration testing results
  • organizational risk assessment results
  • system security plan
  • other relevant documents or records

Interview

  • Organizational personnel with system and services acquisition responsibilities
  • organizational personnel with information security responsibilities
  • organizational personnel with supply chain protection responsibilities

Test

  • Organizational processes for conducting assessments prior to selection, acceptance, or update
  • mechanisms supporting and/or implementing the conducting of assessments prior to selection, acceptance, or update
Related controls
Source record

Authoritative sources