Google BigQuery Viewless Integration

Learn about how the Google BigQuery viewless integration works and what Immuta does in your environment to register your data and keep it in sync

Public preview: This integration is available to all accounts that request to enable it for their tenant. Contact your Immuta representative to enable it.

Immuta policies will not be automatically enforced in Google BigQuery

While you can author and apply subscription and data policies on Google BigQuery data sources within Immuta, these policies will not be enforced natively in the Google BigQuery platform.

To use this integration, contact your Immuta representative.

The Google BigQuery viewless integration allows you to register data from Google BigQuery in Immuta.

What does Immuta do in my environment?

Registering a connection

Google BigQuery is configured and data is registered through connections, an Immuta feature that allows you to register your data objects through a single connection to make data registration more scalable for your organization. Instead of registering schema and databases individually, you can register them all at once and allow Immuta to monitor your data platform for changes so that data sources are added and removed automatically to reflect the state of data in your data platform.

When the connection is registered, Immuta ingests and stores connection metadata in the Immuta metadata database. In the example below, the Immuta application administrator connects the database that contains marketing-data, research-data, and cs-data tables. Immuta registers these tables as data sources and stores the table metadata in the Immuta metadata database.

Immuta presents a hierarchical view of your data that reflects the hierarchy of objects in Google BigQuery after registration is complete:

• Project
• Dataset
• Data object

Beyond making the registration of your data more intuitive, connections provides more control. Instead of performing operations on individual schemas or tables, you can perform operations (such as object sync) at the connection level.

See the Connections reference guide for details about connections and how to manage them. To configure your Google BigQuery viewless integration and register data, see the Register a Google BigQuery connection guide.

Required Google BigQuery privileges

The privileges that the Google BigQuery integration requires align to the least privilege security principle. The table below describes each privilege required by the setup user and the service account.

Google BigQuery privilege	User requiring the privilege	Explanation
roles/iam.serviceAccountCreator roles/iam.serviceAccountAdmin roles/resourcemanager.projectIamAdmin on the project (or be a project owner)	Setup user	This privilege is required so that the setup user can create the service account and custom role for Immuta.
bigquery.datasets.get bigquery.tables.get bigquery.tables.list	Service account	These privileges allow the Immuta service account to get metadata for datasets and their objects.

Maintaining state with Google BigQuery

The following user actions spur various processes in the Google BigQuery viewless integration so that Immuta data remains synchronous with data in Google BigQuery:

• Data source created or updated: Immuta registers data source metadata and stores that metadata in the Immuta metadata database.
• Data source deleted: Immuta deletes the data source metadata from the metadata database.

Supported object types

Object type	Subscription policy support	Data policy support	Request app support
Tables	❌	❌	✅
Views	❌	❌	✅
Materialized views	❌	❌	✅

Immuta policies

Immuta will not apply policies in this integration.

Security and compliance

Authentication methods

The Google BigQuery viewless integration supports the following authentication method to register a connection:

• GCP service account key file: This is the private key file generated when you create a Google Cloud service account and role for Immuta to use to connect to Google BigQuery. These credentials are used by Immuta to register the connection and maintain state between Immuta and Google BigQuery.

Limitations and known issues

The following Immuta features are unsupported:

• Identification
• Subscription and data policies
• Tag ingestion
• Query audit