Drift Cost

I. Formal Definition

The incremental spend incurred when the deployed state of infrastructure diverges from the declared state in source-controlled configuration, typically through manual changes, ad hoc scaling, or unmerged hotfixes. Drift cost is the waste form of configuration drift: a security and reliability problem also produces a budgetary problem. The federation requires drift detection to be continuous, with the dollar magnitude of drift visible to FinOps and SecOps. Drift exceeding fifty thousand dollars per month per environment is escalated for joint review under UFMS-001:2.4.

II. Etymology

A combination of drift, from Old English drifan, to be carried by current, and cost; the term entered DevOps vocabulary in the early 2010s with infrastructure as code.

III. Federation Usage

Federation members maintain continuous drift detection feeding both DevOps and FinOps. Drift dollars are reported in both inform reports. Persistent drift above the threshold is escalated to the joint operations council under MEV-Annex:3.2.

IV. Related Terms

• privilege-drift
• untagged-spend
• orphan-asset
• overprovisioned

V. Authoritative Citations

• UFMS-001:2.4UFMS Article II - Configuration Hygiene
• MEV-Annex:3.2MEV Annex III - Drift Reporting

VI. Citation in BibTeX

@misc{ifo4_glossary_drift_cost,
  title        = {{Drift Cost}},
  author       = {{IFO4 Federation Editorial Board}},
  howpublished = {{IFO4 Federation Glossary, slug \texttt{drift-cost}}},
  year         = {2026},
  url          = {https://ifo4.org/glossary/drift-cost},
  note         = {Category: Waste; key: DriftCost}
}

VII. Challenge This Definition

Federation members and accredited practitioners may challenge any entry under TGS-002:1.7. Filed challenges are routed to the editorial board, triaged into the revision register, and resolved in writing on the public docket. The slug remains stable through any revision.