- In short
- Compliance drift is when a control that is correct at design time silently stops being true in production as configurations change - a data-residency pin, say, becoming false months later after an unrelated change. Without a named owner watching a specific evidence artifact, drift is not detected until an audit or incident surfaces it, and passing an initial constraint pre-filter is not the same as proving ongoing compliance. Controls must be revalidated on a regular cadence, not verified once and assumed permanent.
Full concept guide coming soon
We are building the in-depth, exam-aligned guide for this knowledge point. In the meantime, explore the prerequisites and related concepts below, watch the official Anthropic Academy lessons, and start an adaptive study session to master it with Archie.
Watch and learn
Official Anthropic Academy lessons first, then hand-picked walkthroughs. Videos load only when you press play.
No videos curated for this concept yet
We are still curating the best official and community videos for this topic.
References & primary sources
Adaptive study
Master this concept with Archie
Practice it inside an adaptive study session. Archie, your Socratic AI tutor, tracks your mastery with Bayesian Knowledge Tracing and schedules the perfect next review.