This article discusses how you can use the Stories Workbench to review stories for potential threats in your account.
Cato Detection & Response is an additional layer of security that creates stories for threats. When Cato’s advanced correlation engines analyze traffic data and find a match for a potential threat, they generate a story. The story contains data from traffic flows with common properties that relate to the same threat. The Stories Workbench page shows the details of each story to help you understand and analyze the threats. You can sort and filter the stories to find the most important potential attacks, and then drill-down on a story to further investigate the details.
These are examples of data that a story can include:
-
Sources in your network
-
External targets of network traffic
-
Identification and description of the threat
-
Relevant geolocations
-
Related applications
-
Relevant events
-
Popularity of the target according to Cato internal data
-
Malicious score of the target according to Cato machine learning models
The Stories Workbench page shows a summary of the stories for the potential threats in your account.
Column |
Description |
---|---|
ID |
Unique Cato ID for this story |
Created |
Date of the first traffic flow for the story |
Updated |
Date of the most recent traffic flow for the story |
Criticality |
Cato's risk analysis of the story (values are from 1 - 10) |
Indication |
Indicator of attack for the story. For more about indications, see Using the Indications Catalog |
Source |
IP address, name of device, or SDP user on your network involved in the story |
Engine Type |
The security engine that created the story. |
Status |
|
To provide context when reviewing the stories, you can show the stories in groups defined by details including Source, Indication, Status, and Type. For example, you can show together all of the stories related to a specific source IP address or all of the Cybersquatting stories. This gives you a broader perspective when analyzing the stories, and can help you reach faster and more accurate conclusions.
Each group highlights the criticality levels for the stories in that group, including the number of high, medium, and low criticality stories.
There are three ways to filter the data in the Stories Workbench:
-
Select a preset filter
-
Automatically update the filter with a selected item
-
Manually configure the filter
You can select a preset filter to focus on either Network Operations or Security Operations stories. When you select a preset filter, the story columns most relevant for that type of story are shown by default.
As you hover over an item or field where a filter option is available, the button appears. Click the icon to show the filter options:
-
Add to Filter - Adds the item to the filter, and the Stories Workbench now only shows stories that include this item. For example, if you filter for a specific Criticality score, the page only shows stories with that Criticality.
-
Exclude from Filter - Updates the filter to exclude this item, and the Stories Workbench now only shows stories that do NOT include this item.
You can continue to add items to the filter, click again to update the filter and drill-down further.
The default time range for the Stories Workbench is the previous two days. You can select a different time range to show a longer or shorter time period. For more information, see Setting the Time Range Filter.
The maximum date range for the Stories Workbench is 90 days.
You can manually configure the story filter for greater granularity to analyze the stories. After you configure the filter, it is added to the stories filter bar and the page is automatically updated to show the stories that match the new filter.
To create a filter:
-
In the filter bar, click .
-
Start typing or select the Field.
-
Select the Operator, which determines the relationship between the Field and the Value you are searching for.
-
Select the Value.
-
Click Add Filter. The filter is added to the filter bar and the Stories Workbench is updated to show stories based on the filters.
You can remove each item in the filter separately, or clear the entire filter.
You can click on a story in the Stories Workbench to drill-down and investigate the details in a different page. This page contains a number of widgets that help you evaluate the potential threat identified by the Threat Prevention engine.
The Stories Workbench drill-down includes a tool that lets you create a natural language story description generated by AI, which provides rich context and helps you quickly assess the story. The story summary is generated dynamically to reflect the current state of the story. If the story updates with new information, you can regenerate the summary to reflect the changes.
-
The AI story summary is generated only on-demand by the admin
For robust data security during the transmission of story data to third-party AI services, Cato uses tokenization to ensure all sensitive data remains in the Cato XDR platform. This involves replacing sensitive information with unique identifiers, or "tokens," rendering the data meaningless to unauthorized entities. Sensitive data is never exposed to third-party services. This approach ensures the confidentiality of the story's details, aligning with our commitment to robust data privacy and security standards.
Note
Note: Due to the limitations of generative AI, the information provided in story summaries may occasionally contain inaccuracies.
These are the story drill-down widgets:
Item |
Name |
Description |
||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 |
Story summary |
A summary of basic information about the story, including:
Click to open the Story Actions panel and change story settings such as Analyst Verdict and Status. |
||||||||||||||||||||||||||||
2 |
Shows a timeline of the story, such as changes made to the story verdict and severity, and when new targets related to the story are identified |
|||||||||||||||||||||||||||||
3 |
Details |
Key information for analyzing the story, including a threat description, and MITRE ATT&CK® techniques identified for the threat. Other details include:
For more about the MITRE ATT&CK® framework, see Working with the MITRE ATT&CK® Dashboard.
|
||||||||||||||||||||||||||||
4 |
Source |
Basic information about the devices in your network impacted by the threat |
||||||||||||||||||||||||||||
5 |
Attack Geolocation |
Shows the geolocation for sources in your network (orange locations) and external sources (red locations) related to the threat. Arrows connecting the sources indicate the direction of traffic |
||||||||||||||||||||||||||||
6 |
Target Actions |
Events related to each target, including the following information:
|
||||||||||||||||||||||||||||
7 |
Attack Distribution |
Time distribution of attack related flows.
|
||||||||||||||||||||||||||||
8 |
Targets |
Shows data for the potentially malicious sources outside your network site related to the story.
|
||||||||||||||||||||||||||||
9 |
Attack Related Events |
Shows data for a representative sample of events related to the attack.
|
0 comments
Please sign in to leave a comment.