Configuration management is the discipline of capturing every device’s configuration, keeping a version history, and being able to compare one version — or one device — against another. Compliance is what that history lets you prove.
What it is
At its core it’s three habits applied consistently across the whole estate:
- Capture — take a copy of each device’s configuration, both on a schedule and on demand.
- Version — keep those copies over time, so every device has a history rather than just a current state.
- Compare — diff one point in time against another, or one device against another, to see what differs.
Why it matters
Configuration drift is a quiet source of outages: a change made in a hurry, never logged, that works until the day it doesn’t. When something breaks, recovery depends on having a known-good copy to restore. And regulators and auditors increasingly want evidence — proof that a control is in place everywhere, not a verbal assurance that it usually is. Without a versioned record, “who changed this, and when?” becomes an archaeology project instead of a lookup.
What good looks like
Strong configuration management means scheduled backup so there’s always a recent copy, diff over time and device-to-device so change is visible, and search across the estate so you can prove a control in one query instead of hundreds of logins. Add retention long enough to satisfy audit, and drift detection that flags a configuration that moved without a matching change record, and the routine questions — recovery, compliance, accountability — all become answerable in minutes.