Major New Features
Onboarding Enhancements
- Company Profile: When the Dasera Admin logs into the system for the first time, during the validating Company Profile section of the Onboarding workflow, they will now be able to choose which Compliance Regulations apply to their organization. Based on their selection, Dasera will auto-configure the appropriate built-in classifiers (including Sensitive Data Types and Tags) for Classification Management. Visit our Company Profile article to learn more about this process.
- AWS Infrastructure Onboarding for Dasera-hosted tenants: We have expanded support for IAM Role Based onboarding to our Dasera-hosted tenants (previously supported on just self-hosted instances). We have also added the support for External ID for an additional layer of security and trust when connecting your AWS Infrastructure to your Dasera-hosted tenant.
- Connect a Data Store Wizard Updates: Privilege Analysis now has a Toggle on the Capabilities Tab of the Wizard which allows you to disabled this feature if you wish not to use it. It is automatically Toggled OFF for Data Stores for which Privilege Analysis is not supported or not applicable and cannot be Toggled ON.
Databricks Support for Classification
We have expanded our connector coverage to Databricks. We can now classify sensitive data stored in your Databricks Cloud environment.
To learn more, please visit our Connecting to Databricks Data Stores article.
Synthetic Data Classification (via “is not in Dictionary” Match Condition Support)
Custom Sensitive Data Type match criteria is extended to support the condition “Field Content is not in Dictionary” mainly for Synthetic Data Classification. When this condition is picked, even it 5% of the samples that are being compared against the dictionary provided are not in the dictionary, the field will be classified as this Custom Sensitive Data Type. The threshold for this match condition is more restricted than our usual Custom Sensitive Data Type confidence threshold for better accuracy. It is recommended to use this match condition in combination with the Field Name condition to reduce false positives.
To learn more, please visit our Using Data Dictionaries in Custom Sensitive Data Types article.
Improvements
AWS SNS and GCP Pub/Sub Notification Settings
We now support sending JSON notifications via Google Pub/Sub between different GCP projects. When configuring a GCP Pub/Sub Workflow Channel, you can designate which GCP account should be used for publishing. This requires granting additional permissions to the Dasera-specific service account in GCP. Please see full documentation for permissions needed to enable cross project notification. The same is supported for the AWS SNS service, as well.
To learn more, please visit the article for your particular IaaS provider: