Configuration Drift Detection Plan
Find and fix manual changes to infrastructure.
Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Plan how to detect configuration drift. Infrastructure managed by code: [MANAGED_RESOURCES]. Resources changed by hand in the past: [MANUAL_CHANGES]. Tooling available: [TOOLING]. Define a drift detection process: scheduled plan or compare runs, how to classify drift (benign, risky, urgent), who is alerted and how, and how to decide between updating the code or reverting the change. Provide a triage table with Drift type | Example | Action | Owner | Time to resolve. Include controls to reduce manual changes: restricted permissions, an emergency access procedure with logging, and a review for each emergency change. Suggest metrics to track and a monthly review. Add an escalation policy that defines what counts as an urgent drift (for example, a security rule opened to the internet) and the maximum time to respond. Provide a sample alert message of 60 words and a monthly drift summary format that lists new drift, resolved drift and recurring offenders, so that the process produces learning, not blame.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.