Introducing Cross-Engine ABAC

Cross-engine ABAC enables enterprises to enforce fine-grained access control policies across multiple engines through Unity Catalog.

• •Row and column-level policies are enforced at the catalog layer using tag-based rules and SQL UDFs
• •Supports multiple Iceberg REST-compatible engines including Apache Spark, with DuckDB and Starburst integrations coming
• •Policies are defined once in Unity Catalog instead of being duplicated across separate engines
• •Enforcement happens through Iceberg REST Catalog scan APIs before data reaches external engines

This summary was automatically generated by AI based on the original article and may not be fully accurate.