Introducing Cross-Engine ABAC
Summary
Databricks has announced the Beta of cross-engine ABAC, extending its lakehouse vision for open storage, open access, and unified governance. This new capability enables enterprises to enforce attribute-based access controls (ABAC) defined in Unity Catalog across external engines using Iceberg REST Catalog APIs. Unity Catalog becomes the first catalog to deliver this cross-engine ABAC enforcement, applying tag-based row filters and column masks universally. This eliminates the previous tradeoff where security teams had to duplicate policies across engines or risk over-granting access. Cross-engine ABAC supports the full expressiveness of Unity Catalog policies, including tag-based rules and SQL UDFs, and works with any Iceberg REST client. Currently, it supports Apache Spark via Iceberg-Spark and Delta-Spark connectors, with Starburst and DuckDB integrations planned. The system functions by having Unity Catalog evaluate user entitlements and policies, returning a filtered scan plan to the engine, which then processes only authorized data.
Key takeaway
For MLOps Engineers or Data Architects managing data governance across a multi-engine lakehouse, you should evaluate Databricks' new cross-engine ABAC Beta. This capability allows you to define fine-grained access policies once in Unity Catalog, ensuring consistent enforcement of row filters and column masks across Apache Spark and other Iceberg REST clients. This significantly reduces policy duplication and security risks associated with siloed governance, streamlining your data access management. Consider enabling the preview and testing its integration with your existing Iceberg-Spark or Delta-Spark setups.
Key insights
Unity Catalog's cross-engine ABAC centralizes fine-grained data access policy enforcement across diverse data engines via Iceberg REST Catalog APIs.
Principles
- Unified governance simplifies security.
- Open standards enable broad interoperability.
- Centralized enforcement secures untrusted engines.
Method
External engines send scan requests to Unity Catalog. Unity Catalog evaluates policies, then returns a filtered scan plan, ensuring the engine only processes authorized data.
In practice
- Enable "Cross-engine ABAC" preview.
- Define tag-based row/column policies.
- Query via Iceberg-Spark connector.
Topics
- Unity Catalog
- Attribute-Based Access Control
- Iceberg REST Catalog
- Data Governance
- Lakehouse Architecture
- Apache Spark
Best for: CTO, VP of Engineering/Data, Director of AI/ML, AI Architect, MLOps Engineer, Data Engineer
Related on AIssential
Editorial summary, takeaway, and curation by AIssential. Original article published by Databricks.