Infrastructure Drift Detection
ClosePart of Drift Detection.
- What it is
- The running infrastructure is compared with its declared state so that changes made outside the pipeline are detected.
- Why it matters
- A manual fix during an incident outlives the incident: the running system stops matching the code, and the next deployment either reverts it or hides it.
- You have it when
- Live infrastructure is compared with its declared state on a schedule, in every environment rather than only production, and a difference is reported to the owning team.
What is wrong
No remediation deadline — expected a remediation deadline, actual none
The thing in place is Argo CD reconciliation against Git.
Required as recommended: Required by profile rule(s): CLOUD_CONFIGURATION_BASELINE
Every scope this job would settle
| Environment | Technology | Phase | Control point | Weight |
|---|
| Production | Kubernetes | Operate | Continuous Scan | 2 |
| Production | Kubernetes | Operate | Runtime | 2 |
| Production | Helm | Operate | Continuous Scan | 2 |
| Production | Helm | Operate | Runtime | 2 |
Something you already own
Nothing you already run claims to do this job.
See the whole capabilityChange an answer