Major New Features
Determining Risky Data Stores
Dasera's Data Store Risk Rating answers the question, “Which are the riskiest data stores?” The score is assigned to data store for the overall risk based on misconfiguration, over-privileges and concentration of sensitive data. This score will help you prioritise actions to keep your data stores secure.
Each data stores's risk rating is based on:
| Misconfiguration Risk | Risk due to suboptimal security configuration that leaves sensitive data vulnerable. |
|---|---|
| Over Privileged Data Store Risk (Stale) | Risk due to multiple users with stale privileges. |
| Data Store Sensitive Data Access Risk | Risk due to high concentration of sensitive data. |
Data Store Risk Rating and related risk scores are displayed on Dashboard widgets and Data Store pages.
To learn more, please visit our Data Store Risk Rating article.
Disconnecting Data Stores Governed by Dasera
There are instances where you may no longer need Dasera to monitor a connected data store, including data stores you have since learned are empty, are decommissioned, or were mistakenly connected to begin with. Dasera now provides the ability to disconnect such data stores, which will remove their data from other screens. With this reduction in clutter, the application will only display information related to the data stores which Dasera continues to protect.
To learn more, please visit our Data Store Inventory article.
Scripts for Mass-Connecting Data Stores
Dasera now provides scripts which allow you to connect multiple data stores at once. For customers with a high quantity of data stores, this important activity is now quick & efficient, and you can more-quickly gain insights from our misconfiguration & user privilege analysis features.
Initial scripting support is available for MySQL (both IaaS-hosted & on-premises instances) and GCP BigQuery. To learn more, please visit our related articles:
Improvements and Updates
Data Access Policy & Alerts
Our Data Access Policy Conditions and Alert behavior have been updated with 6.2 to make it scalable across environments with large number of data stores and users.
- The Data Set policy condition granularity is limited to the Schema Level (previously up to Table Level) but if you are trying to see determine violations to a specific sensitive data type or by tags that would not be impacted.
- The Review Condition has been deprecated.
- The Alerts generated now would be by per Data Store/ per user (previously grouped by Data Store). This helps resolving or remediation per user if there was a Automated workflow built for quarantining a User.
To learn more, please visit our Creating New Policies article.
Breadcrumbs for Sub-Level Navigation
Dasera now has page title with breadcrumbs on top of every page to help with navigation and understanding of where you are within the product. These breadcrumbs are clickable on the Data Store Inventory drill-down pages to help navigate through hierarchy of the data store. Also, we now have a universal back button to help go back to previous page.
Support for On-Prem Oracle Data Stores
Dasera has expanded its Oracle connector coverage and can now classify sensitive data stored in your on-prem Oracle environments.
To learn more, please visit our Connecting to Oracle Data Stores article.