Skip to content
Compliance Automation Tools

Home / Glossary / Control drift

Glossary, read 12 Nov 2026

Control drift, defined with a sourced example

All termsThe guides

Control drift in practice

Drift is a timing problem. A control passes at the start of the audit window and fails in month four, and a once-a-year check cannot tell the difference. Vanta's evidence collection article tells teams to monitor for performance drifts, which it says are often caused by misconfigurations or unauthorized changes, and to remediate before they become compliance gaps.

Drift needs a baseline to be measured against. Where the baseline is a system configuration, change control decides whether a change is a deviation or an approved update. See policy exceptions for how a known deviation is recorded.

Example: NIST SP 800-53 Rev. 5 control CM-2, Baseline Configuration, requires teams to develop, document and maintain under configuration control a current baseline configuration of the system and to review and update it. Drift is any departure from that documented baseline.

Sources

  1. vanta.com/resources/automated-evidence-collection-for-compliance-all-you-need-to-know, read 12 Nov 2026
  2. raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json, read 12 Nov 2026

Last reviewed 12 Nov 2026.