Data Governance
One enforcement plane governs every path into the data. Row filters and column masks compile into the query plan; every read carries a classification and a lineage record; and a revoke on the canonical governance edge is the authoritative deny at every serving face.
In this area
| Page | What it covers |
|---|---|
| In-engine enforcement | Row-level security and column masking pushed down into execution: policy that cannot be bypassed |
| Classification and lineage | A classification and a lineage record that travel with every asset and result |
| The authoritative deny | One revoke that denies across the marketplace, Delta Sharing, and the Iceberg REST catalog |
| Schema governance | DDL, replication policy, and classification declared together, so which data crosses which boundary is a property of the schema |
| Data lifecycle | TTL, tombstone purge, compaction, and retention: how data ages, expires, and is reclaimed under policy |
The principle
Governance is part of execution, not a wrapper around it, and it is deny-closed, an ungoverned asset is refused, not open by default. The same control that decides what a query returns decides what a share serves and what the marketplace exposes, from one canonical edge.
Related topics
- Governed reads, the concept this plane rests on.
- Open sharing, enforcement that follows a share out to the recipient.
- Security governance (deny-closed), the action-boundary gate this connects to.
- Security classification, the classification model.