NIST SP 800-53 Rev. 5 CM-6 — Configuration Settings

What this control requires

Establishes, implements, and monitors configuration settings for system components using secure benchmarks, approving deviations as needed. This control supports the Configuration Management System capability within the Configuration Management family.

In plain English

Establishes, implements, and monitors configuration settings for system components using secure benchmarks, approving deviations as needed. In practice, this means you can prove you security 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 Configuration Management, the assessor will trace your implementation back to the catalogue reference (Control CM-6) and look for objective evidence on the latest two assessment cycles.

How to implement

Cloud Posture

CSPM. Run Wiz / Prisma / Defender for Cloud / Security Command Center over every account; auto-ticket findings above your accepted-risk threshold.

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.

Operational checklist

• Security. Document the trigger, the owner and the cadence.
• Configuration. Document the trigger, the owner and the cadence.
• Network. Document the trigger, the owner and the cadence.
• System. Document the trigger, the owner and the cadence.
• Control. Document the trigger, the owner and the cadence.
• Scope: management, system, configuration, settings, components, capability, monitors, system components.

Evidence to collect

• Infra Scan. Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings.

Infrastructure posture tooling (AWS Config, Azure Policy, Nessus) verifies platform hardening. Focus: Configuration Settings.

Common pitfalls

• Treating CSPM findings as a backlog instead of a hot queue: findings older than the policy SLA accumulate until the auditor asks why.
• 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.

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.

• NIST SP 800-171 Rev. 3 3.4.12 — System and Component Configuration for High-Risk Areas
• BSI C5:2020 INQ-02 — INQ-02 Informing Cloud Customers about Investigation Requests
• CIS Controls v8 18.4 — Validate Security Measures
• ISO/IEC 27001:2022 A.5.34 — Privacy and protection of personal identifiable information (PII)

Related controls in NIST SP 800-53 Rev. 5

• Control CM-2 — Baseline Configuration
• Control CM-6(1) — Automated Management, Application, And Verification
• Control CM-2(7) — Configure Systems And Components For High-Risk Areas
• Control CM-6(2) — Respond To Unauthorized Changes
• Control CM-3(8) — Prevent Or Restrict Configuration Changes
• Control SR-11(2) — Configuration Control For Component Service And Repair

References

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

Topics: governance riskcloud postureconfiguration managementnetwork security