Revalidating Data Policy Violations
Once a data policy is triggered by a specified condition, you can use the Scan Jobs tab within the Policy Details to track the rescan status of the data source and violation results return.
Currently rescans are limited to Catalog scan type only.
To rescan for violations
Once you have remediated the data source for the given violation, you can perform a rescan to refresh the data policy against the data source and inspect for a lowered violations count. Rescanning promotes data risk mitigation practices for scenarios like file deletion and updating shared access levels.
This also permits policy managers to know where sensitive files are shared internally/externally so ensure those files have the appropriate access levels. To do this, the data policy conditions will need to reflect the desired access level to detect violations with the incorrect levels.
Rescan of violations is supported for the following data sources:
-
Amazon S3
-
Box
-
Google Drive
-
OneDrive
-
Salesforce
-
SharePoint
-
SMB
Currently rescans are limited to Catalog scan type only. The Rescan option in the Actions selection field is only displayed for data sources that support rescan.