Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Incident risk ranking
Cases are groups of related incidents that combined, indicate a risk to your organization—for example, incidents of data being sent to suspicious destinations or those occurring outside normal office hours. Combining incidents in this way saves you from having to investigate hundreds of incidents and lets you instead focus on a small number of high-risk cases.
Cases are assigned risk scores by a sophisticated analytics engine that you install on a Linux machine. (See the TRITON AP-DATA Installation Guide for details.) If you do not have the analytics engine installed, the Incident Risk Ranking report is unavailable.
Incidents within cases are also ranked according to their number of matches, transaction size, content, breached policies and rules, date and time, and more. For information on the analytical and statistical techniques used to rank and score incidents, see Risk-Based DLP Incident Ranking.
The Incident Risk Ranking report shows the cases with the highest risk scores during the selected time period, along with details for those cases. You specify which scores to display under Settings > General > Reporting—for example, display only cases with a score of 6 and above. Up to 20 cases are shown. (See Setting reporting preferences.) You must have a role with Summary reports permissions to view the report.
Each case is represented by a card such as this:
Cards show the following information:
*
Risk score - The risk score assigned to the case, between 0-10 with 10 being the highest risk. This score is derived by the analytics engine and can be used to assess the security risks in your organization. Scores are based on data accumulated over time. An incident with a score of 2.5 may not pose a high-risk on Monday, but when combined with other incidents from the same source over the week, it might be assigned a higher score. The sample case shows a risk score of 8.9.
*
Classification - Cases are classified as one of 2 things:
*
Suspected data theft - the incidents in this case may indicate an attempt to steal sensitive data. This is based on factors such as statistical information, user and system profiling, the sensitivity of the data, and the risk this incident may impose on the organization.
*
Uncategorized (unknown) - the incidents in this case do not fall into the Suspected Data Theft classification.
The sample case is classified as suspected data theft.
*
Date & Time - The date and time of the last incident that was added to the case. To see incident risk cases for other dates, use the time line shown above the case cards Click a date to display incidents that occurred on that date. Use the scroll bar to see incidents for the previous week. The time line also shows the number of incidents scoring above the selected threshold each day. The picture below shows that there were 16 incidents above the threshold today (Monday).
*
Case ID - Each case has a unique ID, such as ID:163840.
*
My Cases ( ) - Click the flag to add a case to or remove it from a personal case list known as My Cases. When you click the button, the case is added to your list for future reference. You can have up to 200 cases in your My Cases list.
*
Source - The source that originated the incidents in the case—either a person or machine. Click the person icon to view the LDAP role and picture of the source if available. There can be multiple sources for each case.
*
Reason - Each case lists reasons why the case is included in the report. For example:
jbrown@gmail.com sent credit card and other sensitive content (almost 300 matches) to 3 common email addresses.
*
Information () - To view case details, click the information icon on the card. In the example above, there were 390 PII breaches and an unusually high number of credit card incidents. Some descriptions show classification accuracy. Red up arrows indicate that an incident increases a case's risk score. Green down arrows indicate that an incident lowers the risk score.
*
Next/Previous Page () - Click this button to see the next page of the card for more details. The content varies by case. The second page shows the source and destinations relevant to the case (those that pose a risk) and any files that are involved.
*
Number of incidents - The number of incidents in the case are shown as a link on the bottom of the card. Click this link to drill down to the current Incidents report, filtered according to the case, so you can investigate the incidents further.
Toolbar
The following buttons are on the report's toolbar:
*
My Cases - Shows the cases that you have flagged.
*
Settings - Opens the Settings > General > Reporting page where you can configure reporting preferences such as risk score threshold—e.g., show only cases exceeding a score of 8.0.
*
Export to PDF- Exports all the cases that are currently displayed to PDF.

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Copyright 2016 Forcepoint LLC. All rights reserved.