NIST SP 800-171 Rev. 3·Requirement 3.17.1·high·Component: System and Services Acquisition

What this control requires

This control requires developing a supply chain risk management plan to address risks associated with the entire lifecycle of systems and system components, including research, development, design, manufacturing, acquisition, operations, and disposal. The plan should be regularly reviewed and updated and must be protected from unauthorized disclosure. This control supports the Supply Chain Risk Management Plan capability within the System and Services Acquisition (3.17) family.
— NIST SP 800-171 Rev. 3, Requirement 3.17.1

In plain English

This control requires developing a supply chain risk management plan to address risks associated with the entire lifecycle of systems and system components, including research, development, design, manufacturing, acquisition, operations, and disposal. In practice, this means you can prove you access management-level controls on a defined cadence.

Why it matters

DoD contractors and their subcontractors must implement all 100 SP 800-171 requirements to keep CUI handling contracts. Gaps are scored against the SPRS scoring methodology; below a 110-point starting score, each unmet requirement deducts points and a below-threshold score can disqualify a bid.

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 C3PAO conducting a CMMC Level 2 assessment uses NIST SP 800-171A objectives. They expect a System Security Plan (SSP), Plan of Action & Milestones (POA&M) for any gaps, and objective evidence (configurations, ticket records, training records) for every requirement.

Within System and Services Acquisition, the assessor will trace your implementation back to the catalogue reference (Requirement 3.17.1) 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.
  • System. Document the trigger, the owner and the cadence.
  • Risk. Document the trigger, the owner and the cadence.
  • Plan. Document the trigger, the owner and the cadence.
  • Supply. Document the trigger, the owner and the cadence.
  • Scope: management, system components, chain risk management plan, research, development, design, acquisition, operations.

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.
  • Infra Scan. Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings.

Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Focus: Supply Chain Risk Management Plan.

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.

Related controls in NIST SP 800-171 Rev. 3

References

Topics: governance riskidentity managementaccess reviewprivileged accesssecure development