Security Operations Efficiency dashboard
Summarize
Summarized using AI
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.
Summary of Security Operations Efficiency Dashboard
The Security Operations Efficiency dashboard enables Security Operations Center (SOC) managers to assess the efficiency of their team through performance metrics. This tool is essential for tracking overall SOC performance and identifying areas for improvement over time.
Show less
Key Features
- Analyst Efficiency Tab: Analyze individual analyst performance metrics such as average security incidents worked, closed incidents, and resolution times.
- Detection and Response Effectiveness Tab: Measure the effectiveness of incident responses, including true positive rates and false positives, to evaluate the accuracy of security incident handling.
- Incident Risk Score Analysis Tab: Assess the total risk exposure and normalized workloads for security analysts based on incident classifications.
- Incident Stage Analysis Tab: Monitor the status and age of open incidents across different stages of the incident response process.
Key Outcomes
Utilizing this dashboard allows SOC managers to:
- Identify trends in incident handling and team performance over time.
- Enhance resource allocation by understanding individual analyst workloads and efficiency.
- Improve incident resolution times and decrease the average age of open incidents.
- Evaluate and refine detection mechanisms based on false positive rates and incident sources.
This comprehensive analysis ultimately leads to a more efficient and responsive security operation, enabling better management of security incidents.
Security operations center (SOC) managers can view overall efficiency metrics and measure the individual performance of the SOC team members in the organization.
The SOC manager can use the Performance Analytics dashboard to improve efficiency and develop a picture of how SOC is performing in both general and specific areas over time.
Analyst Efficiency tab
Click any of the indicators to drill down for further details. For
example, click the indicator in the Average security incidents
worked per analyst section.
The graph shows that the number of open security incidents have increased
from 0 in March to over 40 in May. Notice the data displayed in the
header:
- Trend indicator: Shows the change in number of open incidents in the latest time period for which the data has been collected. This chart shows data for the period March 2019 to May 2019 and the number of open incidents has increased by 19 in the month of May. Analyst efficiency is better if the number of open incidents has decreased over a period of time.
- No. of scores: The period for which the data has been collected (March to May 2019).
- Sum: The number of new open incidents for the period between March and May.
- Change: The number of new open incidents between March and April.
- Average: The average number of open incidents per analyst for the selected period.
| Indicator | Description |
|---|---|
| Average security incidents worked per analyst | Average number of open security incidents
per analyst for the specified period. The formula
used is [[Number of open security
incidents / By month AVG +]]/[[Number of Security
Agents]] |
| Closed security incidents per analyst | The total number of incidents closed by
each analyst in the selected category in the
specified period. The formula used is
[Number of closed security incidents >
Security Incident Category = <category_name> /
By month SUM +]]/[[Number of Security Agents / By
month AVG +]] |
| Average security incident resolution | The average time taken by each analyst to
close security incidents in the specified period.
The formula used to show the result in days is
([[Summed duration of closed security
incidents > Security Incident Category =
<category_name> / By month AVG +]] / [[Number
of closed security incidents > Security Incident
Category = <category_name> / By month AVG +]])
/ 24 |
| Average security incident age | The average number of days for which
security incidents remain open for each analyst.
The formula used to show the result in days is
([[Summed age of open security incidents >
Security Incident Category = <category_name> /
By month AVG +]]/ [[Number of open security
incidents > Security Incident Category =
<category_name> / By month AVG +]]) /
24 |
| Security incident backlog analysis | The total number of open security incidents in the specified period. Select an option from the Breakdown list to view the backlog for each analyst, security group, priority, and so on. You can also compare the number of open security incidents between two selected months. |
| Closed security incident analysis | The total number of security incidents that are closed in the specified period. Select an option from the Breakdown list to view the count for each analyst, security group, priority, and so on. You can also compare the number of security incidents that were closed between two selected months. |
| Security incident age | The average number of days for security
incidents remain open in the specified period.
Select an option from the Breakdown list to view
the security incident age for each analyst,
security group, priority, and so on. The formula
used to show the result in days is
([[Summed age of open security incidents >
Security Incident Category = <category_name> >
Security Assignment Group = <group_name> / By
month AVG +]]/ [[Number of open security incidents
> Security Incident Category = <category_name>
> Security Assignment Group = <group_name> / By
month AVG +]]) / 24 |
| Security incident resolution time | The average number of days taken to resolve
security incidents during the specified period.
Select an option from the Breakdown list to view
the security incident resolution time for each
analyst, security group, priority, and so on. The
formula used to show the result in days is
([[Summed duration of closed security
incidents > Security Incident Category = Malicious
code activity > Security Assigned To = John Ashby
/ By month AVG +]] / [[Number of closed security
incidents > Security Incident Category = Malicious
code activity > Security Assigned To = John Ashby
/ By month AVG +]]) / 24 |
Detection and Response Effectiveness tab
| Indicator | Description |
|---|---|
| True positive incidents | Percentage of true positive security
incidents in the selected category for the
specified period. The formula used is
(1-([[Number of false positive security
incidents > Security Incident Category = Malicious
code activity / By month SUM +]] / [[Number of
closed security incidents > Security Incident
Category = Malicious code activity / By month SUM
+]])) * 100 |
| False positive critical incidents | Percentage of false positive critical
security incidents in the selected category for
the specified period. The formula used is
([[Number of false positive security
incidents > Security Incident Risk Score =
Critical Risk > Security Incident Category =
Malicious code activity / By month SUM +]] /
[[Number of closed security incidents > Security
Incident Category = Malicious code activity / By
month SUM +]]) * 100
Note: Any security
incident where the Closed code = Invalid
vulnerability or False positive is
treated as a false positive
incident |
| Mean false positive risk score | Average monthly risk score of closed
security incidents that were identified as false
positive incidents. A lower risk score indicates
that the security analysts spent lesser time
analyzing false positive incidents. The formula
used is ([[Number of false positive
security incidents > Security Incident Risk Score
= Critical Risk > Security Incident Category =
Malicious code activity / By month SUM +]] /
[[Number of closed security incidents > Security
Incident Category = Malicious code activity / By
month SUM +]]) * 100 |
| False positive security incident duration | Average number of days that the security
analysts spent in investigating false positive
incidents. The formula used is ([[Summed
duration of false positive security incidents]] /
[[Number of false positive security incidents]]) /
24 |
| Security incident source effectiveness | Percentage of true positive security
incidents identified by a specific source for the
specified period. The source can be email, network
activity,customer support, and so on. This data
helps measure the effectiveness of the security
incident source. The formula used is
(1-([[Number of false positive security incidents
> Security Incident Category = Malicious code
activity > Security Incident Source = IDS/IPS / By
month SUM +]] / [[Number of closed security
incidents > Security Incident Category = Malicious
code activity > Security Incident Source = IDS/IPS
/ By month SUM +]])) * 100 |
| Security incident source volume analysis | Number of closed security incidents for current month for each Security incident source. You can also compare the number of security incidents for each source type between two selected months. |
| Security incident backlog analysis | The total number of open security incidents
in the specified period and the average number of
days for which the incidents remain open. You can
also compare the number of open security incidents
between two selected months. The formula used to
calculate the average backlog period is
([[Summed age of open security incidents >
Security Incident Category = Malicious code
activity]]/ [[Number of open security incidents >
Security Incident Category = Malicious code
activity]]) / 24 |
| Closed security incident analysis | The total number of closed security
incidents in the specified period and the average
resolution time for these incidents. The formula
used to calculate the average resolution time is
([[Summed duration of closed security
incidents > Security Incident Category = Malicious
code activity]] / [[Number of closed security
incidents > Security Incident Category = Malicious
code activity]]) / 24 |
Incident Risk Score Analysis tab
| Indicator | Description |
|---|---|
| Total risk exposure analysis | Total number of open incidents in each risk category (low, moderate, and critical) in the specified period. You can also compare the number of incidents in the different risk categories between two months. |
| Normalized security analyst work by risk score | The total risk score for each security
analyst for the specified period. This is
calculated based on the number of true positive
security incidents that the security analyst
closed. The formula used is [[Summed Risk
Score of Closed Security Incidents > Security
Incident Category = Malicious code activity >
Security Assigned To = SI Admin / By month SUM +]]
- [[Summed Risk Score of False Positive Security
Incidents > Security Incident Category = Malicious
code activity > Security Assigned To = SI Admin /
By month SUM +]] |
| Security analyst work by mean risk score | The average risk score for each security
analyst for the specified period. The formula used
is [[Summed Risk Score of Closed Security
Incidents > Security Incident Category = Malicious
code activity > Security Assigned To = SI Admin /
By month AVG +]] - [[Summed Risk Score of False
Positive Security Incidents > Security Incident
Category = Malicious code activity > Security
Assigned To = SI Admin / By month AVG
+]] |
Security Incident Stage Analysis tab
You can see the number of open incidents on a specific day and the status (analysis, draft, contain, eradicate, recover, or review) of these incidents. On each stage, you can view average age, affected CIs, response tasks, and so on. Click on a link to view additional details or the breakdown of these incidents.