Lakehouse supports BigQuery row-level security and column-level security with dynamic data masking on Apache Iceberg tables in the Lakehouse runtime catalog (GA). You can restrict which rows principals can see and mask sensitive column values by managing these policies with GoogleSQL DDL statements in BigQuery. On catalogs that use credential vending mode, the Apache Iceberg REST catalog endpoint vends storage credentials only to principals that have unmasked access to every protected column and, if the table has row-level access policies, unfiltered row access.
You can manage and version control SQL scripts and notebooks with BigQuery Studio Git repositories, which provide a streamlined, folder-based integration with remote Git repositories. This feature is generally available (GA).
You can query the
INFORMATION_SCHEMA.ROW_ACCESS_POLICIES view
to retrieve metadata about active
row-level access policies and inspect
filter predicates across a dataset or region. This feature is
generally available
(GA).
Text from the Google Cloud release notes, licensed under CC BY 4.0. Source: Google Cloud release notes.
Free. Unsubscribe any time.
Related updates
BigQuery Security center and jobs explorer improvements generally available
BigQuery Iceberg tables get flexible column names, gemini-embedding-2 is GA
BigQuery Lakehouse cross-cloud caching and remote catalog access generally available
BigQuery Lakehouse Hive catalog endpoint and Dataproc Metastore migration generally available