Configuration Management
What is Configuration Management?
Configuration ManagementThe discipline of establishing, recording, and enforcing the desired state of systems and applications so configurations remain known, consistent, and secure.
Configuration management defines the authoritative settings for operating systems, network devices, applications, and cloud resources, and uses tooling such as Ansible, Puppet, Chef, Terraform, or Kubernetes operators to apply and reconcile them. Combined with version control and policy-as-code, it enables drift detection, repeatable rebuilds, and proof of compliance with hardening benchmarks like CIS or DISA STIG.
Security-focused configuration management (SecCM) is codified in NIST SP 800-128 (published August 2011, errata October 2019), which supports the Configuration Management (CM) control family of NIST SP 800-53 and describes four phases: planning, identifying and implementing a secure baseline, controlling changes through a change-control board with security impact analysis, and monitoring for unauthorised drift. Automation is driven by machine-readable standards — the Security Content Automation Protocol (SCAP) and NIST's National Checklist Program let scanners assess hosts against published baselines without hand inspection.
From a security viewpoint, SecCM eliminates one of the most common breach root causes: silent configuration drift, where an emergency change, a forgotten debug flag, or a default credential quietly reopens a hole that hardening had closed. Cloud misconfiguration — public object storage, over-broad IAM roles, disabled logging — is consistently among the leading causes of cloud data exposure, which is why policy-as-code and continuous reconciliation have become baseline practice.
flowchart LR
A[Define secure baseline<br/>CIS / DISA STIG] --> B[Store as code<br/>version control]
B --> C[Apply with CM tooling<br/>Ansible / Terraform]
C --> D[Running systems]
D --> E{Continuous scan<br/>SCAP / drift check}
E -->|Compliant| D
E -->|Drift detected| F[Change control<br/>+ security impact analysis]
F --> B● Examples
- 01
Terraform definitions enforcing that every S3 bucket has encryption and public-access blocks enabled.
- 02
Ansible playbooks that bring all SSH servers back to the approved CIS Benchmark configuration.
● Frequently asked questions
What is Configuration Management?
The discipline of establishing, recording, and enforcing the desired state of systems and applications so configurations remain known, consistent, and secure. It belongs to the Defense & Operations category of cybersecurity.
What does Configuration Management mean?
The discipline of establishing, recording, and enforcing the desired state of systems and applications so configurations remain known, consistent, and secure.
How do you defend against Configuration Management?
Defences for Configuration Management typically combine technical controls and operational practices, as detailed in the full definition above.
What are other names for Configuration Management?
Common alternative names include: Config management, CM.