SOC workload measures the volume and complexity of alerts, incidents, and investigations the team handles over a defined period. It covers both reactive work, responding to detected threats, and proactive work, including threat hunting, use case development, and process improvement.
Core indicators:
- Alert volume provides the baseline input load and the reference point against which changes in the detection environment are assessed
- Incident severity distribution shows the proportion of alert volume representing genuine significant threats versus routine events and false positives
- Analyst capacity utilisation measures the proportion of available analyst hours consumed by the workload, which is the leading indicator of burnout risk before it becomes visible in quality degradation or staff attrition
Why it matters:
- An overloaded SOC is a risk management problem, not only a resource management problem
- Analysts working at or beyond capacity miss alerts, make triage errors, and defer the proactive work that keeps the detection programme current
- Workload data provides the evidence that resource allocation conversations require to be driven by data rather than intuition
Management approaches:
- Tiered escalation routes straightforward alert types to Tier One analysts while reserving Tier Two and Tier Three capacity for the complex investigations that require their depth
- SOAR automation handles the repetitive initial processing steps that consume analyst time without requiring human judgment, preserving capacity for the decisions and investigations that genuinely benefit from human involvement
Tool Usage Metrics #
Keep reading with a free Eristotle account.
Every document across our Bodies of Knowledge is free to read once you are signed in. No payment, no tier.
