Ensures that a system's performance, functional, and physical attributes remain consistent with its requirements, design, and operational information throughout its life.

To refer to the disciplined process of managing changes to configuration items so that system integrity is maintained over time.

When setting up a new system, updating software or hardware configurations, releasing new versions, or conducting audits.

Software engineering, DevOps, systems administration, embedded systems, telecommunications, aerospace.

identify configuration items → record baseline → track changes → audit revisions

configuration management

• version control
• baseline
• configuration item
• change control
• audit
• baseline configuration
• configuration item (CI)
• configuration item database (CMDB)

• configuration control
• change management

Failing to establish a baseline, neglecting to document changes, allowing ad-hoc changes without tracking.

change management, release management, asset management

Coming from Git: assuming all configuration files are version‑controlled → non‑versioned items like runtime‑generated configs may be missed.

• DevOps practices
• release management
• change control
• asset management

Encompasses both administrative procedures and technical tools for tracking and controlling changes.

Conveys a systematic, disciplined approach to maintaining system integrity.

Think of a baseline configuration that records every change like a lab notebook.

Effective configuration management often relies on a CMDB to store relationships between items and to support impact analysis during changes.

Advanced configuration management with automation and CI/CD pipelines