Governance Policies and Findings
Review detected conditions with consistent evidence and accountability.
Governance findings translate supported cost and metadata conditions into reviewable work. Examples include missing owners/applications, spend that remains unattributed, aged unattached resources, selected idle/oversized signals and operational issues in dual run or stranded source cost.
Finding interpretation
A finding is created under a specific rule, observed time and evidence scope. A missing-owner finding is a data-governance problem; it is not proof that the AWS resource is wasteful. Insufficient evidence should default to a review state, not a definitive “inefficient” claim.
Lifecycle
Findings can be investigated, assigned, resolved or excepted through the appropriate workflow. Idempotent background jobs should avoid duplicate copies of the same condition and maintain historical context when a condition stops appearing.
From finding to action
The owner decides whether to correct metadata, create an allocation rule, change operational process, or propose an optimization action. CoreFinOps remains read-only toward the customer's cloud resources.
Security
Evidence and freshness
Review collection time, connected AWS scope, applicable policy and any missing source. A failed inventory collection should not erase previously valid findings or make the estate appear clean.