Major New Features

Object-Level Tagging

With Dasera's new Object-Level Tagging feature, your classification activities have become richer & more-robust. Tags allow you to group sensitive data for many use case types, from compliance to industry needs, or general business requirements. Tagged data is then used in Policy Conditions to automate data governance activities.

Now with 5.1, you can tag at any level of the data set hierarchy, not just fields. This includes datastores, databases, schemas, and tables. In addition, Tag Inheritance allows you to assign tags to a specific data set level and have all of its data sets inherit those tags. For example, tagging a table also applies that tag to its fields. For Data Owners, this saves time and boosts efficiency.

The ability to leverage data set tags in policies above the field-level will be available soon in an upcoming release.

Early Configuration Analysis 

Configuration Analysis is now supported at time of Data Store Discovery. Previously, this was only available once Data Stores were connected. Now with 5.1 for all Data Stores that support config scanning, Dasera can now highlight potential risk if any of the security configurations are misconfigured:

• Backup is Disabled
• Encryption is Disabled
• Public Accessibility is Enabled or set to a Permissive Firewall

Once a Data Store is connected, Dasera can calculate an actual Misconfiguration Risk Score, which takes into account the concentration of sensitive fields and gauges the potential impacts of breaches due to misconfiguration.

Archive Discovered Data Stores

Data Stores of lesser importance can now be archived, which hides them from the UI and prevents them from over-shadowing the truly-important Data Stores. When archiving, you can supply the reason, so others are aware why the Data Store was archived. 

Archived Data Stores remain available within Dasera under a new Archived tab, and there they can be unarchived if necessary.

Permission Check Bypass

Connecting to some data stores can take longer than expected based due to the number of objects within them. To save time upfront and improve user experience, we have introduced a permission check bypass feature which shows you a Warning message if the permission checks are taking longer than 60 seconds but allows to start scanning. Permissions checks still continue to be performed in the background and failures will be reported in the Administration → Activity Logs → System Activity  Tab.

AWS CloudFormation and Terraform Templates

CloudFormation and Terraform Templates are now available for deploying Dasera in AWS environments and configuring the Dasera Service Account User. These speed up the onboarding process and provides a simplified user experience.

Improvements

Custom Query Log Mappings

While connecting to data stores, you can provide custom query logs to take advantage of Dasera's Data-in-Use Monitoring capability. The custom query logs can be in any CSV or JSON format.  You now have the flexibility to configure the indices or keys in any order and provide Dasera with the mapping.  

Additionally the S3 bucket in which the query logs are located can be live in any of the accounts onboarded into Dasera and no longer needs to reside in the same account as the Data Store being connected.

New Dasera Knowledge Base

To facilitate ease-of-use, we have revamped our customer knowledge base. Besides featuring a cleaner look-and-feel, the new KB also includes these benefits:

• Improved search experience: results are returned as you type, and excerpts are displayed to assist with accessing the most-relevant article.
• Better organization: articles for AWS, GCP, and Azure are now grouped together in specific collections, which provides for a single destination for accessing all subjects for your cloud provider.

To access the new knowledge base, please log into the Dasera application and visit the in-application Support menu.