Integrations Overview

Immuta does not require users to learn a new API or language to access protected data. Instead, Immuta integrates with existing tools and data platforms while remaining invisible to downstream consumers.

The table below outlines features supported by each of Immuta's data platform integrations.

	Marketplace	Subscription policies	Data policies	Identification	Impersonation	Query audit	Tag ingestion
Amazon Redshift integration	✅	✅	✅	✅	❌	❌	❌
Amazon Redshift Spectrum integration	✅	✅	✅	✅	✅	❌	❌
Amazon S3	✅	✅	❌	✅	❌	❌	❌
AWS Lake Formation	✅	✅	❌	✅	❌	❌	✅
Azure Synapse Analytics	✅	✅	✅	✅	✅	❌	❌
Databricks Lakebase	✅	✅	❌	✅	❌	❌	❌
Databricks Spark	✅	✅	✅	✅	✅	✅	❌
Databricks Unity Catalog	✅	✅	✅	✅	❌	✅	✅
Google BigQuery	✅	✅	✅	✅	❌	❌	❌
MariaDB	✅	❌	❌	❌	❌	❌	❌
MySQL	✅	❌	❌	❌	❌	❌	❌
Oracle	✅	❌	❌	✅	❌	N/A	❌
PostgreSQL	✅	✅	❌	✅	❌	❌	❌
Snowflake	✅	✅	✅	✅	Supported with caveats	✅	✅
SQL Server	✅	❌	❌	✅	❌	❌	❌
Starburst (Trino)	✅	✅	✅	✅	✅	✅	❌
Teradata	✅	✅	❌	✅	❌	❌	❌

Subscription policy support matrix

The table below illustrates the subscription policy access types supported by each integration. If a data platform isn't included in the table, that integration does not support any subscription policies. For more details about read and write access policy support for these data platforms, see the Subscription policy access types reference guide.

Data platform	Read access policies	Write access policies
Amazon Redshift	✅	✅
Amazon Redshift Spectrum	✅	❌ View-based integrations are read-only
Amazon S3	✅	✅
AWS Lake Formation	✅	✅
Azure Synapse Analytics	✅	❌ View-based integrations are read-only
Databricks Lakebase	✅	✅
Databricks Spark	✅	❌ Write access is controlled through workspaces and scratch paths
Databricks Unity Catalog	✅	✅
Google BigQuery	✅	❌ View-based integrations are read-only
PostgreSQL	✅	✅
Snowflake	✅	✅
Starburst (Trino)	✅	✅
Teradaata	✅	❌

Data policy support matrix

The table below outlines the types of data policies supported for various data platforms. If a data platform isn't included in the table, that integration does not support any data policies.

For details about each of these policies, see the Data policy types page.

	Amazon Redshift	Amazon Redshift Spectrum	Azure Synapse Analytics	Databricks Spark	Databricks Unity Catalog	Google BigQuery	Snowflake	Starburst (Trino)
Conditional masking	❌	✅	✅	✅	✅	❌	✅	✅
Custom function	❌	✅	✅	✅	✅	✅	✅	✅
Format preserving masking	❌	❌	❌	❌	❌	❌	✅	❌
Hashing	❌	✅	✅	✅	✅	✅	✅	✅
Regex	❌	✅	❌	✅	✅	✅	✅	✅
Masking fields within STRUCT columns	❌	❌	❌	✅	Supported with caveats	❌	❌	❌
Minimize	❌	✅	✅	✅	✅	✅	✅	✅
Only show data by time	❌	✅	✅	✅	✅	✅	✅	✅
Only show rows (matching)	✅	✅	✅	✅	✅	✅	✅	✅
Randomized response	❌	❌	❌	❌	❌	❌	✅	❌
Replace with NULL or constant	✅	✅	✅	Supported with caveats	✅	✅	✅	✅
Reversible masking	❌	✅	❌	✅	❌	❌	✅	✅
Rounding	❌	✅	✅	✅	✅	✅	✅	✅
WHERE clause	❌	✅	✅	✅	✅	✅	✅	✅

Identification support matrix

Identification has varied support for data sources from different technologies based on the identifier type. For details about how identification works in Immuta, see the Data identification page.

Technology	Regex	Dictionary	Column name regex
Amazon Redshift	❌	❌	❌
Amazon Redshift Spectrum	✅	✅	✅
Amazon S3	❌	❌	✅
AWS Lake Formation	❌	❌	✅
Azure Synapse Analytics	❌	❌	✅
Databricks Lakebase	❌	❌	✅
Databricks Spark	✅	✅	✅
Databricks Unity Catalog	✅	✅	✅
Google BigQuery	❌	❌	✅
MariaDB	❌	❌	❌
MySQL	❌	❌	❌
Oracle	❌	❌	✅
PostgreSQL	❌	❌	✅
Snowflake	✅	✅	✅
SQL Server	❌	❌	✅
Starburst (Trino)	✅	✅	✅
Teradata	❌	❌	✅

Query audit support for platform queries

The table below outlines what information is included in the query audit logs for each integration where query audit is supported.

	Snowflake	Databricks Spark	Databricks Unity Catalog	Starburst (Trino)
Table and user coverage	Registered data sources and users	Registered data sources and users	All tables and users	Registered data sources and users
Object queried	✅	✅	✅	✅
Columns returned	✅	❌	✅	✅
Rows returned	✅	❌	✅	✅
Query text	✅	✅	✅	✅
Unauthorized information	Limited support	✅	✅	❌

Legend:

• ✅ This is available and the information is included in audit logs.

• ❌ This is not available and the information is not included in audit logs.