What's New

Fixed an issue where a classification scan on a data source completed but had a table failure that was exacerbated by its large size, which prevented the table from being classified.

We now have an additional stored procedure for onboarding that allows you to use your own service user, role and warehouse. This new stored procedure is helpful in the situations where you must adhere to a specific naming convention and run into issues when using our default service user.

By default, this stored procedure grants access to everything in your Snowflake account, but you can specify a list of databases to limit what the role can access.

The new stored procedure also grants “MANAGE GRANTS” to ALTR’s service user, enabling support for upcoming features related to the automation of grants on securable Snowflake objects.

Updated documentation to follow. In the mean time, reach out to ALTR Support for assistance.

If a column or table no longer existed in Snowflake because an error occurred on the Snowflake side, you were unable to force disconnect it from ALTR. This issue has been fixed and you can now successfully force disconnect columns and tables from ALTR when an error occurs in Snowflake.

We are excited to announce automatic tagging — a new feature that provides the ability to map ALTR classification results to Snowflake object tags and to automatically assign those tags to Snowflake columns, both in the UI and the API. This feature is available to ALTR Enterprise accounts for both Snowflake and Google DLP classification. Learn more about automatic tagging.

We have improved the Upgrade page by adding easy navigation to ALTR’s pricing details so you can see what features are included in your current plan and a way to contact ALTR to obtain add-on features or to upgrade your plan.

To provide a more consistent user experience, we have standardized the following elements across the user interface:

Styling of the Snowflake Partner Connect onboarding for setting up ALTR accounts for first-time users has been updated to match the rest of the UI in order to provide a consistent user experience.

An error occurred when you tried to view the System Audit page in UTC time zone. To fix this issue, we encoded dates and now use the correct UTC format without a time zone offset, allowing you to view records on the System Audit page as expected.

You can now configure custom roles when connecting Snowflake object tags in the UI by turning on the ADVANCED: Enable custom roles switch for the tag. Learn more.

You can now import new allowed values for a Snowflake object tag into ALTR by clicking the Refresh Allowed Values button on the Tag Details page. This feature makes new allowed values available when defining ALTR policies. Learn more.

You can now set up detokenization on Snowflake object tags through the ALTR UI. You can also continue to perform this task through the API. Learn more.

When you clicked the Help Center icon on a page during the Snowflake Partner Connect onboarding and contacted support, the Email field did not require a valid email address. For a smoother user experience, the Contact Support modal now opens and uses the email address associated with your ALTR account to message ALTR Support.

You can now disconnect a tag from the ALTR UI if you no longer want ALTR to enforce access governance to columns with that tag. Refer to Disconnecting Tags for more information.

We update two terms throughout the ALTR UI to align with industry standards:

We updated our online documentation to include an optional step to restrict the ALTR service user access to our IPs, providing a more robust security strategy. Refer to ALTR's Snowflake Service User for more information.

The classifier list on classification reports now displays in order of most columns to least to allow you more efficiently consume and understand the data.

As an ALTR administrator, you are now able to refresh the list of key-value pairs allowed on a Snowflake object tag via the API. When the refresh is triggered, ALTR ingests any new allowable values present on the indicated Snowflake object tag. This feature allows you to create policies on new tag values without having to run an object tag import.

The tabs on the Data Management page were reordered and now display as Classification Report, Tags, Columns so you first land on the Classification Report instead of Columns. This change provides a better first-time user flow for adding new data as the tabs now display in the order of tasks to be performed.

You can now define policy directly on tag names in order to control policy at the tag level without specifying each value; access is the same for all values associated with that tag. On the Create Lock page, Tag Name and Value is the default option, but you can now optionally select Tag Name only. Refer to Creating Column Access Policies in ALTR for more information including use cases for each policy option.

The columnName in the clientScatteredFields table, which stores the governed columns, was set to varchar(45) so any columnName with more than 45 characters was truncated. This name truncation caused errors, including a failure to disconnect columns. To fix this issue, the character limit on columnName was increased from 45 to 255.

You can now connect Snowflake object tags through our UI on the Tags page. Using ALTR’s Tag-Based Policy integration enables easy scaling of data masking and avoids complications relating to schema name changes and data cloning. You can continue to perform this task through the API, but our recommendation is to use the UI. Refer to Connecting Tags for more information.

Two videos were replaced by text to provide a better, always-up-to-date user experience:

An issue with the CORS preflight handler prevented access to the Tags page when using the Microsoft OS. To fix this issue, the Tags page is accessible as expected.

We fixed an issue that restricted an underscore (_) from being in a Snowflake hostname. We now permit underscores in Snowflake hostnames.

We now offer the ability to view the status of ALTR-connected Snowflake object tags through our UI on the new Tags page ( Data Configuration → Data Management → Tags). Users can continue to perform this task through the API, but our recommendation is to use the UI. Refer to View Tag Connection Status for more information.

We fixed an issue that when a classification job failed, the backend cache was not cleared, which displayed an In Progress status in the UI. Now when a job fails, it is correctly marked as failed in ALTR’s UI.

We made several enhancements to the Classification Report page to provide a better user experience:

We fixed an issue where an unintentional scroll bar appeared at the bottom of the Classification Report page when there were 10+ classification reports. Now this scroll bar does not appear.

Minor technical and stability improvements.

ALTR's UI has been updated to standardize the styling of modals across the application.

Fixed an issue where invited ALTR administrators were not properly entering a "pending" state. This prevented customers from re-sending invite links to ALTR administrators after the original invite had expired.

Minor technical and stability improvements.

The ALTR UI now automatically trims whitespace when submitting Two-Factor Authentication (2FA) codes during login.

Fixed an issue that would occasionally cause classification jobs to stall.

Fixed an issue where schema object caches failed to update if there were more than 80 schemas within a database.

Fixed an issue where audit logs would not properly trigger for Vaulted Tokenization V2 Endpoints

Several bugs were fixed that caused errors in the Vaulted Tokenization API.