Skip to content
CTEM Vendors

Home / Glossary / Security control drift

Glossary, read 12 Nov 2026

Security control drift, defined for a CTEM program

All termsStage Coverage Map

Security control drift in practice

Drift happens without anyone deciding it: an exception added for a migration and never removed, a log source that stops forwarding, an EDR policy reset by an update, a detection rule whose field mapping changed. Each looks harmless alone. Together they mean the control that passed last quarter may fail today, and nobody sees an error.

CTEM handles drift by re-validating on a schedule and treating any regression as a new exposure. Picus markets catching silent failures from configuration drift as part of its control validation, as the vendor describes it. Configuration monitoring catches setting changes; only testing catches a control that is configured correctly but no longer works.

An example

CISA's BOD 25-01 (December 17, 2024) set June 20, 2025 as the date for federal agencies to implement mandatory SCuBA policies, starting with Microsoft Office 365.

Source, read 12 Nov 2026.

Sources

  1. https://csrc.nist.gov/glossary/term/baseline_configuration, read 12 Nov 2026
  2. https://csrc.nist.gov/pubs/sp/800/128/upd1/final, read 12 Nov 2026
  3. https://www.cisa.gov/news-events/directives/bod-25-01-implementing-secure-practices-cloud-services, read 12 Nov 2026

Last reviewed 12 Nov 2026.