Viewing Alerts
Last updated
Last updated
To view all the alerts created, click on the Alerts icon on the left navigation bar of the Playbooks window.
This will show a grid-view of all resolved and unresolved alerts.
Let us look at an example of Google Drive alert. Here, we can see that 3 rule sets have been violated and thus 3 alerts have been triggered. This alert has impacted 67 objects and 80 entities.
Click on the alert. This will show the rule sets that have been violated.
In Fig.22 we can see that the 3 rule sets that have been violated are ‘ExternalUsers’, ‘Client Info’ and ‘InternalUsers’.
The External User cards are sorted based on the number of objects accessible by external users, with the alerts having the highest number of externally accessible objects appearing at the top. This sorting mechanism enables users to quickly identify and prioritize alerts that require immediate attention due to the potential risk associated with external user access.
Alerts 2.0 Enhancements:
Sorting in Card View:
When the external user field is populated for an alert, the card view on the Alerts page will be sorted based on the number of objects the user has access to.
This enhancement helps users prioritize their alert handling based on the impact of each alert, focusing on the alerts with the highest number of objects accessible by external users.
The card view provides a clear and intuitive representation of the alerts, displaying relevant information such as the policy type, rule set, data source, and the number of objects impacted.
Pagination Improvements:
To optimize performance and improve the user experience, pagination has been implemented on the Alerts page.
Users can now navigate through alerts in smaller, more manageable sets, rather than loading all alerts on a single page.
Users can easily navigate between pages using the pagination controls, which include options like "Previous
," "Next
," and specific page numbers.
The Attributes section displays the specific attributes that were detected in the objects impacted by the alert. It provides an overview of the different types of attributes found, such as Address
, First Name
, Middle Name
, Name
, and USA Social Security Number (SSN)
. For each attribute, it shows the sensitivity level (e.g., Medium, High) and the number of files or attribute instances associated with it.
The Entities Impacted section shows the individuals or entities whose sensitive data was detected in the objects impacted by the alert. It presents a list of the entity names along with the number of attributes associated with each entity and the number of objects in which their data was found. This view allows users to quickly identify the specific entities affected by the alert and assess the scope of the data exposure.
File classification-based alerts are generated when a document's file classification matches the conditions defined in the corresponding labeling policy.
In the Alerts page, file classification-based alerts are displayed alongside other types of alerts.
The alert details include information about the file classification that triggered the alert, the associated label, and the affected documents.