Session

From Data Portability to Governance Portability: The Future of Cross-Platform Governance

Overview

ExperienceIn Person
TrackGovernance & Security
IndustryEnterprise Technology
TechnologiesLakeflow
Skill LevelIntermediate

Enterprises run on multiple data platforms — Unity Catalog, Snowflake, Lake Formation, BigQuery, and many others. PII may be tagged in one catalog, masked in another, and ignored in a third. Open table formats solved data portability, but governance metadata remains siloed inside each data platform.

 

This talk explores how enterprises can unify governance across platforms using labels exchange: carrying governance tags, classifications, and business metadata across catalogs through Apache Iceberg REST Catalog APIs. We'll cover why cross-platform governance is becoming the next federated data pain point, what's emerging in the Apache Iceberg ecosystem, and how teams can operate multi-platform architectures.

Session Speakers

Alex Jiang

/Product Manager
Databricks

Speaker placeholderIMAGE COMING SOON

Andrei Tserakhau

/Engineering Manager
Databricks

Full Summary

From portable data to portable governance: the next chapter for open catalogs

Open table formats solved a hard analytics problem by letting a single physical copy of data serve many engines. As organizations spread workloads across Databricks Platform, Snowflake, Glue, Fabric, and open source engines, a new gap has appeared. Policies, tags, and classifications still live inside each catalog, so teams duplicate governance and lose consistency. A shared data governance layer that moves with the data is the next step, and understanding how Unity Catalog table access controls underpin fine-grained enforcement helps illustrate why a portable model matters.

FAQ


No. Engines that already rely on credential vending request a scan plan as usual. The catalog applies row filters and column masks server side and returns sanitized file references, so the engine runs a normal query without implementing fine-grained policy logic.

No. The consuming platform evaluates and enforces its own policies in its native expression language. What travels between catalogs is the metadata, such as tags and classifications, that those policies depend on.

The exchange uses the Iceberg REST catalog protocol. Using an open standard preserves extensibility so that any catalog or platform can participate.

External tools often copy entire policy sets and identities, which is expensive and brittle. The described model moves only the minimal metadata needed to make a decision, keeping enforcement local while unifying the context.

No. Open table formats and federation allow a table registered in one platform to be queried from another without copying the files. The governance work extends that same no-copy principle to the metadata that governs the data.