Join our Newsletter — 33% off our NHI Course
Home› Glossary› Cyber Security› Cloud Drift
Cyber Security

Cloud Drift

← Back to Glossary
By NHI Mgmt Group Updated October 31, 2026 Domain: Cyber Security

Cloud drift is the gap between the intended state of cloud infrastructure and what is actually running. It happens when resources, configurations, or permissions change over time without being brought back under policy control, often creating avoidable spend, security exposure, and operational inconsistency.

What Cloud Drift Really Means

Cloud drift is not just “things changed.” It is the practical mismatch between what policy, IaC, or platform standards say should exist and what is actually deployed. That gap can appear in configurations, permissions, network exposure, identities, logging, tagging, or resource sprawl, and it is often gradual enough to escape notice until cost, risk, or reliability degrades.

In mature environments, drift is usually a sign that the operating model has weakened somewhere, for example, through manual hotfixes, inconsistent change control, or ad hoc exceptions that were never reconciled back into the approved baseline.

Why Cloud Drift Becomes a Security and Operations Problem

Drift matters because the cloud is enforced by code, policy, and control planes, so even small deviations can create real exposure. A forgotten security group rule, an overbroad role, or a resource that no longer matches the intended landing zone can widen attack surface, break segmentation assumptions, or create inconsistent audit evidence. The same problem also undermines resilience when recovery steps depend on a baseline that no longer exists.

Drift is especially dangerous when configuration, privilege, and identity changes accumulate across accounts, subscriptions, or projects faster than teams can verify them. In practice, the risk is not the change itself, but the fact that the change is no longer governed.

NHIMG’s Cloud Misconfiguration Guide is a useful companion here because it covers the control failures that often sit behind drift, including open services, wildcard IAM, static keys, policy as code, and drift detection.

How Organisations Detect Cloud Drift

Detecting drift usually starts with comparing declared state to observed state across infrastructure-as-code, cloud inventories, policy engines, and account-level configuration snapshots. Asset inventory matters because drift is impossible to govern if the organisation cannot see all accounts, regions, projects, clusters, and exceptions that exist.

Detection also needs to cover changes that are technically valid but still undesirable, such as a newly exposed endpoint, a permission expansion, or a resource that has moved outside the expected compliance boundary. Vendor-native tools, config scanning, and periodic reconciliations all help, but they only work when the intended baseline is explicit and current.

For identity-heavy environments, drift can also show up as cross-cloud inconsistency in roles, federation paths, and privilege boundaries. Multi-Cloud Identity Guide helps frame that problem because identity drift is often the part of cloud drift that creates the highest blast radius.

Reducing Cloud Drift With Governance and Automation

Cloud drift is reduced by making the desired state enforceable, not just documented. That means using policy as code, approval workflows, and controlled deployment paths so changes are expressed through reviewable mechanisms rather than one-off console edits. When exceptions are necessary, they should be time-bound and explicitly owned.

Automated reconciliation is also important because cloud environments change continuously. Teams should treat drift detection as a routine control, not a periodic cleanup exercise, and they should make remediation part of normal operations rather than an emergency response after something breaks.

Practically, the goal is to keep the cloud close to a governed baseline so that security posture, permissions, and operational behaviour remain predictable even as services scale and teams move quickly.

Change discipline is easier to sustain when the organisation treats the cloud control plane as the system of record. In that model, untracked manual change is not just technical debt, it is a governance failure.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

CIS Controls v8, NIST CSF 2.0 and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
CIS Controls v8CIS-4 — Secure Configuration of Enterprise Assets and SoftwareCloud drift is controlled by maintaining approved baselines and detecting config changes.
Recommendation — Enforce secure baselines and continuously detect configuration drift across cloud assets.
NIST CSF 2.0PR.PO-01 — Policy, Processes, and ProceduresCloud drift reflects a gap between intended policy and what is running.
ID.AM-01 — Physical Devices and Systems InventoryDrift cannot be governed without knowing what cloud resources actually exist.
Recommendation — Define and maintain cloud configuration policy so deviations are visible and actionable. Keep an accurate cloud asset inventory to compare intended and actual state.
NIST SP 800-53 Rev 5CM-2 — Baseline ConfigurationCloud drift is deviation from a managed baseline that should be established and tracked.
CM-6 — Configuration SettingsPermissions and resource settings that drift are governed through configuration control.
Recommendation — Maintain approved baselines and compare running cloud state against them. Standardize and monitor configuration settings to prevent uncontrolled cloud deviations.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org