IFO4
Loading...Provisioned infrastructure that continues to operate and incur charges despite being unused, unowned, or detached from any production workload. Zombie infrastructure differs from idle resources by the presence of running processes that consume resources without producing utility. The federation treats zombie infrastructure as a Tier-2 finding because it both wastes spend and complicates security posture by widening the attack surface. Detection must run continuously and remediation must follow a documented decommissioning playbook under UFMS-001:2.4(c).
A cultural metaphor borrowed from horror fiction; the term entered IT operations vocabulary in the early 2000s and was applied to cloud spend in the late 2010s.
Federation members run zombie detection at least weekly. Zombie findings are joint FinOps and SecOps tickets under TGS-002:2.3. Decommissioning evidence is required before the finding can be closed in the federation registry.
@misc{ifo4_glossary_zombie_infrastructure,
title = {{Zombie Infrastructure}},
author = {{IFO4 Federation Editorial Board}},
howpublished = {{IFO4 Federation Glossary, slug \texttt{zombie-infrastructure}}},
year = {2026},
url = {https://ifo4.org/glossary/zombie-infrastructure},
note = {Category: Waste; key: ZombieInfrastructure}
}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.