Immuta v2022.4.0 Release Notes

Immuta v2022.4.6

Immuta 2022.4.6 was released May 2, 2023.

Immuta v2022.4.6 Bug Fix

Running an external catalog sync did not trigger policy updates when only table tags had changed. If users only added or removed table tags, global policy updates were not applied to data sources.

Immuta v2022.4.5

Immuta 2022.4.5 was released March 28, 2023.

Immuta v2022.4.5 Bug Fixes

• When using SCIM to sync an identity manager with Immuta, removing a user from a group in the identity manager did not remove the user from that group in the remote database in the following integrations:

  • Snowflake
  • Redshift
  • Synapse

  This issue could allow that user to retain access to data if they were removed from a group that was granted access by a policy.

• When using the Immuta CLI to clone and save policies, the logic operator (AND or OR) selected between multiple tags was not stored; instead, OR was always used once the policy was saved. For example, if a policy like "Mask columns tagged Discovered . PII and Discovered . Country . USA" was cloned and then saved with the CLI, the OR logic operator was used, and the policy was saved as "Discovered . PII or Discovered . Country . USA".

Immuta v2022.4.4

Immuta 2022.5.2 was released January 25, 2023.

v2022.4.4 Bug Fixes

• Snowflake, Redshift, and Azure Synapse integrations:
  • If a combined global subscription policy was applied to a data source and a user updated a global data policy (create, update, delete) that also applied to that data source, the data policy was not applied to the data source. Consequently, a user querying that table could see values of masked columns in plaintext.
  • If an existing global subscription policy and an existing global data policy applied to the same data source, then modifications to that data source (or the creation of a new data source targeted by those policies), only the global subscription policy was applied to the data source. Consequently, a user querying that table could see values of masked columns in plaintext.

Immuta v2022.4.3

Immuta 2022.4.3 was released November 22, 2022.

Immuta v2022.4.3 Bug Fixes

• Azure Synapse Analytics: If a user was granted access to about 1300 data sources, access to those tables was delayed.
• Deleting an integration on the App Settings page and saving the configuration caused the Immuta UI to crash.

v2022.4.3 Known Bugs

• Editing a schema project to a database that already exists fails.
• Users cannot create an S3 data source using an instance role using the UI; they must use the API.

Immuta v2022.4.2

Immuta 2022.4.2 was released November 17, 2022.

Immuta v2022.4.2 Bug Fixes

• The data source Relationships tab only displayed up to 10 associated projects.
• If creating the Immuta database failed in the Snowflake without Snowflake Governance Controls or Databricks SQL integration, the error returned was incorrect.
• Removed historical schema monitoring metrics that contained database connection strings.
• Subqueries that referenced a table that didn't exist never resolved.
• Policies:
  • Disabling a Global conditional masking policy on a data source could sometimes disable all policies or none of the policies on the data source.
  • If users submitted a Global Policy payload to the API that was missing the subscriptionType from the actions, the Global Policies page broke when trying to display Subscription Policies.
  • Global Subscription Policies that contained the @hasTagAsAttribute variable caused errors and degraded performance.
  • Snowflake with Snowflake Governance Features: Changing a column's masking policy type resulted in errors until users manually synced the policy in Immuta.
• Redshift:
  • Users were unable to query tables that had a policy with a Limit usage to purpose(s) <ANY PURPOSE> applied to them.
  • There were error-handling inconsistencies between the Immuta UI and the database logs.
• Vulnerabilities:
  • CVE-2022-3602
  • CVE-2022-39353

v2022.4.2 Known Bugs

• Editing a schema project to a database that already exists fails.
• Users cannot create an S3 data source using an instance role using the UI; they must use the API.

Immuta v2022.4.1

Immuta 2022.4.1 was released October 26, 2022.

v2022.4.1 Bug Fixes

• When configured with ADFS, the Redshift integration was not creating views for Immuta data sources properly.
• Vulnerabilities:
  • CVE-2022-3517
  • CVE-2022-37616
  • CVE-2022-39299

v2022.4.1 Known Bugs

• Editing a schema project to a database that already exists fails.
• Users cannot create an S3 data source using an instance role using the UI; they must use the API.

Deprecations and Breaking Changes

Deprecated Databases

Deprecated items remain in the product with minimal support until their end of life date.

v2022.4.0 Migration Notes

• All users must be on Immuta version 2020.2 or greater to migrate directly to 2022.4.

Immuta v2022.4.0

Immuta 2022.4.0 was released October 20, 2022.

v2022.4.0 Bug Fixes

• Deleting a tag hierarchy deleted any tags with a like name. For example, deleting the tag department would also delete the tag department_marketing.
• The Refresh External Tags button appeared on the Tag page even if no external catalogs were configured.
• Users couldn't change the schema detection owners for schema projects.
• Collibra: If multiple values were assigned to an attribute in Collibra, they were added as a single tag in Immuta. For example, if an attribute list called Color contained values Blue, Green, and Yellow, and Blue and Green were selected in Collibra, Immuta displayed the data tag as Color.Blue,Green. Instead, Immuta should have created two tags: Color.Blue and Color.Green.
• Webhooks that were listening to setUserAuthorizations were not triggered.
• Deleting a Data Policy did not enable the Save Policy button.
• With Approve to Promote enabled, adding a comment to a policy did not enable the Save Policy button.
• When no backup files were present to restore in a Single Node Docker deployment, new instances did not start properly.

v2022.4.0 Known Bugs

• Editing a schema project to a database that already exists fails.
• Users cannot create an S3 data source using an instance role using the UI; they must use the API.

Deprecations and Breaking Changes

Deprecated Databases

Deprecated items remain in the product with minimal support until their end of life date.

v2022.4.0 Migration Notes

• All users must be on Immuta version 2020.2 or greater to migrate directly to 2022.4.