Netwrix Data Classification v5.7.11.1 — Release Notes

Products Data Classification News
,
1

data-classification-patch-5-7-11-1
data-classification-patch-5-7-11-11920×960 205 KB

Want the full details? Click the link below!

Download Netwrix Data Classification 5.7.11.1 here!

What’s New in v5.7.11.1

MySQL Support in the SQL Server Source

Netwrix Data Classification now supports MySQL as a database type within the SQL Server source. Organizations can connect to MySQL database servers to scan, classify, and monitor sensitive data stored in relational databases. The implementation follows the same collection model as other SQL source types, making setup straightforward for teams already familiar with the SQL connector. This adds MySQL to the list of supported database server sources alongside Microsoft SQL Server and Oracle.

PostgreSQL Support in the SQL Server Source

Netwrix Data Classification now supports PostgreSQL as a database type within the SQL Server source. Organizations can connect to PostgreSQL servers to discover and classify sensitive content stored across their relational database environments. The implementation follows the same collection model as other SQL source types, making setup straightforward for teams already familiar with the SQL connector. This adds PostgreSQL to the list of supported database server sources alongside Microsoft SQL Server and Oracle.

Browse Classified Documents from Unindexed Sources

The Taxonomies Browse view can now display classified documents from sources that are not configured for full-text indexing. This ensures complete visibility into classification results across all source types, including Exchange and other connector types that classify content but do not support search indexing. Users can toggle the option to include unindexed sources when reviewing taxonomy assignments.

Updated Financial Records Taxonomy with Proximity Matching

The Financial Records taxonomy has been updated to use proximity match rules for the SWIFT bank identifier code (BIC) pattern. These refinements require related financial terms to appear near the SWIFT BIC pattern before a match is confirmed, reducing false positive classifications in documents that contain BIC-like patterns without other financial context.

Bug Fixes and Miscellaneous Updates

Server

  • Restored column sorting on the Sources grid and Invalid File Types table (#431459)
  • Added scheduled automatic expunging of deleted file records (#395669)
  • Converted database columns to support Unicode characters (#432488)
  • Fixed workflow wizard incorrectly displaying a validation error after removing any condition (#338923)
  • Added support for passwords up to 256 characters (#417539)
  • Updated Credentials taxonomy to match password-related terms case-insensitively (#424055)
  • Fixed required terms extraction generating incorrect multi-word terms (#371480)
  • Fixed semi-colons being incorrectly stripped from metadata values (#425302)
  • Clarified MIP sensitivity label configuration options for GCC High and DoD environments (#437146)
  • Fixed errors occurring when the server is configured for FIPS compliance (#435561)
  • Fixed Duplicate Detection report returning false positives in file exact-match mode (#436005)
  • Fixed report subscription emails failing when no username is configured for the mail server (#418593)

Connectors

  • Fixed SharePoint crawl error when item permission assignments are uninitialized (#411696)

Need help with this update?

There are many different ways to get help with our products!

Situation Action
If you feel the product is broken and not working as intended… Contact Support
If you have a question you’d like to ask other experts… Create a discussion in the community: Data Classification > Discussions & Questions
If you have a feature request… Let our product team know directly: Data Classification > Ideas
If you have something cool to show… Show everyone what you built: Data Classification > Show & Tell

What are your thoughts?

We are always happy to hear from our users on what you like, and what you hope to see in the future. Please, share your thoughts below!

Data Classification Bug Fix List
2

Will the Taxonomy update wipe out any custom modifications that we have made? Like if we added another clue or remove a clue that came out-of-the-box at install time?

3

Hey Marc,

If you have custom clues set for your taxaonomies, then you would need to ensure that you have “Retain Custom Clues” set before you do the update or you could lose them.

image
image810×554 29 KB

If you have the score altered of a default clue, the score will be reset. A custom clue will not be changed or deleted as long as you use the “retain” option.

1 Like
4

I don’t recognize that screen. Where do you see that option?

5

Good afternoon, @mscirri.

This step is in the “After the Upgrade” steps of our KB on how to update NDC, where you will need to navigate the UI to update the Taxonomies to start using any and all new settings that come with this release.

Please know that if you are already using a fully custom Taxonomy, and not edits to an existing default/prebuilt Taxonomy, this option may not appear. If you are updating a prebuilt taxonomy, select the “Yes” option with the setting “update this prebuilt taxonomy” and click Next, and then on the next page, select the “Retain custom clues” option.

image
image658×394 12.7 KB

Please know that if you made any changes to the scoring to predefined clues in a taxonomy, their values will reset, but any custom clues will not be touched as long as you use the “retain” option.

Also know with the “Financial Records” update listed above, if you have any custom Proximity Matching applied to Regex rules, they will be replaced with predefined Proximity Matching rules with this patch.

If you wish to discuss this further, I would be happy to open a ticket with you to go more in depth about this.

1 Like
6

Ahhh, OK> I thought the taxonomies were part of the software update. I like that they are separate. Thank you !!!

1 Like