Drift detection is the identification of systems, workloads, or configurations that have diverged from an approved or expected state. It matters because unauthorized or accidental change quietly erodes trust in both infrastructure and security controls.
What is Drift Detection?
Drift may appear in manifests, runtime behavior, packages, permissions, or configuration values. Detecting it helps teams spot manual changes, compromise, and policy violations before they become normalized or forgotten.
What Drift Detection Commonly Supports
Common uses include configuration assurance, incident detection, immutable infrastructure practice, and compliance monitoring.
Drift Detection vs. Assumed Configuration Consistency
Drift detection measures whether real state still matches intended state. Assumed consistency trusts that nothing changed without verifying it.
Frequently Asked Questions
Why is drift detection important?
Because environments change constantly, and unobserved drift often hides both risk and operational confusion.
Can drift be benign?
Yes, but even benign drift deserves review because it still weakens confidence in what the system should be.
