NIST SP 800-171 Rev. 3·Requirement 3.4.1·high·Component: Configuration Management

What this control requires

This control requires the development and Maintenance of a current baseline configuration of the system under configuration control. The baseline must be reviewed and updated at defined intervals or when system components are installed or modified. Baseline configurations document the system's components, operational procedures, network topology, and architecture, serving as the foundation for future system builds and changes. This control supports the Configuration Management System capability within the Configuration Management (3.4) family.
— NIST SP 800-171 Rev. 3, Requirement 3.4.1

In plain English

This control requires the development and Maintenance of a current baseline configuration of the system under configuration control. In practice, this means you can prove you baseline 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 Configuration Management, the assessor will trace your implementation back to the catalogue reference (Requirement 3.4.1) and look for objective evidence on the latest two assessment cycles.

How to implement

Configuration Management

Policy-as-code. Codify the control as Service Control Policies (AWS), Azure Policy initiatives, or Organisation Policy (GCP) so the platform enforces what the document promises.

IaC. Gate Terraform / Pulumi / CloudFormation changes with Checkov / tfsec / OPA so misconfigurations never reach production.

Drift. Run a CSPM (Wiz / Prisma / Defender for Cloud / Security Command Center) over every account and route findings to a single risk register.

Network Security

AWS. VPC Flow Logs to S3, default-deny security groups, AWS Network Firewall for north-south, and Transit Gateway for hub-and-spoke segmentation.

Azure. NSGs with deny-by-default, Azure Firewall Premium with TLS inspection, Private Endpoints for PaaS, and Microsoft Defender for Cloud's secure score for drift.

GCP. VPC Service Controls perimeters around sensitive APIs, Cloud NGFW Enterprise for L7 inspection, Private Service Connect for managed services.

Policy Management

Docs. Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.

Operational checklist

  • Baseline. Document the trigger, the owner and the cadence.
  • Configuration. Document the trigger, the owner and the cadence.
  • System. Document the trigger, the owner and the cadence.
  • Maintenance. Document the trigger, the owner and the cadence.
  • Risk. Document the trigger, the owner and the cadence.
  • Scope: management, configuration, security, maintenance, procedures, system components, development.

Evidence to collect

  • Policy Document. A signed and version-controlled policy / standard / procedure document.
  • Infra Scan. Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings.

Signed policy or standard documents the safeguard. Focus: Baseline Configuration.

Common pitfalls

  • Manual cloud-console changes that never make it back to Terraform — drift accumulates until the next outage forces a reconciliation.
  • Default-allow egress rules; East-West traffic with no segmentation; jump hosts on the public internet with password auth.
  • Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.
  • 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 riskconfiguration managementnetwork securitypolicy managementsecure development