IFO4
Loading...A formal, enforceable specification of the metadata that must be applied to every provisioned infrastructure resource for the resource to be eligible to incur charges in a federation member's account hierarchy. A tagging policy is not a guideline; it is enforced at provisioning time through provider native controls or admission webhooks, and resources that fail the policy are denied creation or quarantined within a fixed window. The federation requires that the policy be version-controlled, reviewed at least annually, and tied to the cost-allocation coverage ratio.
Tagging entered cloud finance through the AWS resource-tagging API in 2010; the formal policy construct emerged with provider organisation services in the late 2010s.
Federation members must publish their tagging policy as part of the accreditation evidence pack. A policy that is not enforced at provisioning time is reported as advisory under MEV-Annex:3.2 and does not satisfy the allocation-coverage requirement.
@misc{ifo4_glossary_tagging_policy,
title = {{Tagging Policy}},
author = {{IFO4 Federation Editorial Board}},
howpublished = {{IFO4 Federation Glossary, slug \texttt{tagging-policy}}},
year = {2026},
url = {https://ifo4.org/glossary/tagging-policy},
note = {Category: FinOps; key: TaggingPolicy}
}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.