Every sensitive data asset has its catalog ownership field filled in, or the missing owner is reported into a defined workflow. Ownership must be filled in eventually for sensitive data created in the cloud or migrated there. Automation opportunities: trigger workflows that force population when new assets are created; automate periodic review of ownership and review when an owner leaves or moves; trigger escalation for gaps; recommend owners from the nature and ownership of similar data. Certification test steps: confirm the catalog exists; create entries with and without owners; confirm metadata scanning is enabled on a recurring schedule; report populated and unpopulated ownership; confirm unowned sensitive assets are sent to remediation automatically; check that each listed owner is a current employee and is authorized to own that asset.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.