Immuta Actions and Activities: Snowflake SQL references

Immuta Activity: 'High Cardinality' SQLs in Snowflake

  • query is executed by the datasource ingestion Snowflake user

  • query is not executed by Immuta <db name>_SYSTEM_ACCOUNT user.

SELECT "ID", "FIRST_NAME", "LAST_NAME", "EMAIL", "GENDER", "RACE", "SSN", "DEPT", "JOB", "SKILLS", "SALARY", "TYPE", "BRAND_ID" FROM "BC_DATA"."POV_DATA_0717"."IMMUTA_FAKEHR" LIMIT 1000;

--this is SQL referenced to high cardinality job against the table being ingested to Immuta
SELECT approx_count_distinct("ID") AS approx FROM "BC_DATA"."POV_DATA_0717"."IMMUTA_FAKEHR";

Immuta Activity: Fingerprint job SQL(s) on Snowflake

  • query is executed by the datasource ingestion Snowflake user

  • query is not executed by Immuta <db name>_SYSTEM_ACCOUNT user.

  • Fingerprint is only needed for few Immuta Policy type, e.g.,

    • Format Preserving Masking

    • K-Anonymization

    • Randomized Response

  • Recommend to run Fingerprint on datasources planned to use the above data-policies.

  • More details here.

Immuta Fingerprint SQL-1 in Snowflake:
Immuta Fingerprint SQL-2 in Snowflake:
Immuta Fingerprint SQL-3 in Snowflake:
Immuta Fingerprint SQL-4 in Snowflake:
Immuta Fingerprint SQL-5 Snowflake:

Immuta Activity: NativeSDD job in Snowflake:

  • query is executed by the datasource ingestion Snowflake user

  • query is not executed by Immuta <db name>_SYSTEM_ACCOUNT user.

Immuta NativeSDD SQL in Snowflake:

Immuta Activity: when onboarding datasource to Immuta from Snowflake:

  • query is executed by the datasource ingestion Snowflake user

  • query is not executed by Immuta <db name>_SYSTEM_ACCOUNT user.

  • Enhanced Onboarding is different since high level metadata(database name, schema name, and table names) already crawled or through object-sync.

Immuta Activities: disable or remove of datasources in Immuta

  • datasources/tables in Immuta will NOT be deleted.

  • policy objects will be DROP/UNSET if tables were impacted by row-access or column-masking objects.

  • SQL activities are performed by the Immuta <db name>_SYSTEM_ACCOUNT user, which manages the Immuta-Snowflake integration.

  • SQL various depending on Immuta policies - primarily to remove policy objects and revoke GRANTs to Immuta-created xxx_POLICY_xxx and xxx_USER_xxx roles.

Last updated