Process Mining use cases for security incidents
Summarize
Summary of Process Mining Use Cases for Security Incidents
This guide outlines various Process Mining use cases designed to enhance the resolution efficiency of security incidents. By utilizing these analysis methods, ServiceNow customers can identify and address inefficiencies in their incident management processes.
Show less
Key Features
- Multi-hop Analysis: Identifies incidents reassigned multiple times, helping to pinpoint delays in resolution. Customers can filter incidents by the average number of steps and minimum records to find those that took longer routes.
- SLA Breach Analysis: Analyzes incidents that have breached SLAs to improve adherence. Users can filter incidents based on SLA criteria to identify breaches and analyze the corresponding routes.
- Priority Analysis: Reviews the priority assignment process to ensure incidents are correctly prioritized. This involves identifying incidents initially marked as critical that had their priority lowered.
- Bottleneck Analysis: Detects unusual state transitions and delays in incident handling. Customers can filter for specific bottlenecks to optimize the workflow.
- Long Time to Start than Resolve: Examines incidents that took too long to reach the Draft state but were resolved quickly after. Filters can be set to analyze delays before closure.
Key Outcomes
By implementing these Process Mining use cases, ServiceNow customers can expect to:
- Enhance the speed and efficiency of security incident resolutions.
- Improve SLA compliance and reduce breach occurrences.
- Optimize priority assignments, ensuring critical incidents receive the necessary attention.
- Identify and eliminate bottlenecks in the incident management workflow.
- Gain insights into process delays to enhance overall incident handling strategies.
The following Process Mining use cases provide various analysis methods that you can use to identify inefficiencies during the resolution of your security incidents.
Multi-hop analysis
Security incidents that are reassigned multiple times to different teams might result in a resolution delay. By analyzing the reasons of reassignments for such security incidents, and where the incidents are held up for longer durations, you can improve the overall efficiency.
- Navigate to .
- Select Assignment group.
- Open a project, and navigate to Analyst Workbench.
When you open a mined process optimization project, by default the Analyst Workbench opens.
- Select Variation Analysis.
- Select the filter (
) icon, and set the filter similar to the following:
- Steps greater than the average number of steps.
- Records greater than the minimum number of records that have taken a longer route.Note:You can configure the values as per your requirement.
- Select Apply.
All the records that match the filter criteria appear. Select a record to view the closure route of the record.
- Select a record, and then select Show Route.
The route traversed by the record appears. You can use this route to identify the step where the incidents were held up for a longer duration than expected.
SLA breach analysis
You can use process mining to analyze security incidents that have breached a certain SLA (Service Level Agreement.)
- Navigate to .
- Open a project, and navigate to Analyst Workbench.
When you open a mined process optimization project, by default the Analyst Workbench opens.
- From the Advanced filters, select Conditions.
- Select the arrow corresponding to Related List Condition.
- Set the conditions similar to the following:
- Use the Select list to select the Task SLA table.
- Set the value of the Greater than or equal to field to 1.
- Set the value of Has breached to True.
- To identify security incidents which breached a specific SLA, set a SLA definition filter.
- Select Apply.
All the records that match the conditions appear. Select a record to view the route of the record for analysis.
Priority analysis
You can use the process mining to review and improve the existing priority assignment process to your security incidents.
- Navigate to .
- Open a project, and navigate to Analyst Workbench.
When you open a mined process optimization project, by default the Analyst Workbench opens.
- Select Priority.
- From the Advanced filters, select Transitions.
- In Advanced filter on transitions, configure the following:
- Set Priority is 1 - Critical.
- Select Eventually followed By
- Priority is not 1 - Critical.
- Select Apply all chains.
The map shows all the security incidents that were assigned a priority 1 and their priority was later lowered.
Bottleneck analysis
You can use the process mining to review the state transitions of your security incidents. This analysis identifies the transitions that are not usual and the time delay caused because of such.
- Navigate to .
- Open a project, and navigate to Analyst Workbench.
When you open a mined process optimization project, by default the Analyst Workbench opens.
- Select Bottleneck Analysis from the Model Options.
The screen displays the state transitions for the security incidents.
- Select the Filter by to identify bottleneck transitions. Alternatively, use the search bar to search for bottleneck transitions. For example, to identify incidents which were moved to other states from the Closed state, use "Closed " or "Closed -".
Long time to start than resolve
You can use the process mining to review the incidents that take a long time to get to the Draft state, but then were closed in a relatively shorter time.
- Navigate to .
- Open a project, and navigate to Analyst Workbench.
When you open a mined process optimization project, by default the Analyst Workbench opens.
- From the Advanced filters, select Transitions.
- In Advanced filter on transitions, configure the following:
- Set State (Incident) is Draft.
- Select Eventually followed By
- Select Add constraints and set From as 2 days.
- Select Add next activity.
- Set State (Incident) is In Analysis.
- Select Eventually followed By
- Select Add constraints and set Up to as 30 minutes.
- Select Add next activity.
- Select Eventually followed By
- Select Add constraints and set Up to as 30 minutes.
- Set State (Incident) is Closed.
- Select Apply all chains.
- Select Breakdown Filters and sort by Longest Avg Duration.