Lineage information is available for all sensitive data and at the least shows where the data came from when ingested, or where in the cloud it was created; regulated organizations use it to evidence that regulatory report figures come from an authoritative source. Automation opportunities: capture where each item of data with a specified classification came from when it was migrated to the cloud; capture source-to-target lineage whenever such data moves inside the cloud; record destination lineage of such data leaving the cloud for on-premises or another cloud. Certification test steps: confirm the catalog exists and scanning recurs; produce a lineage report for an asset and confirm it includes at least the ingestion or creation source; create a sensitive asset and see its creation reflected; change an asset's source or target and see the lineage report reflect it.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.