
Good security decisions need sustainable working conditions
A Security Operations Center depends on people making sound decisions under pressure. Analysts investigate suspicious activity, connect incomplete evidence and decide what needs immediate attention. When every shift becomes a race to clear an endless queue, careful investigation becomes harder to sustain. The answer is not simply to hire people who can handle stress. A lasting SOC needs useful alerts, realistic coverage, accessible expertise and clear ownership. Retaining analysts and maintaining detection quality belong in the same conversation.
When alerts compete with attention
Alert fatigue develops when the volume or repetition of alerts makes meaningful assessment harder. IBM describes how low-quality data, missing context and fragmented tools contribute to the problem. Alert fatigue and burnout are not interchangeable: reducing noise does not resolve every workload or management issue. Ask how much of a shift goes into understanding meaningful threats, and how much goes into repeatedly dismissing avoidable noise. The same unhelpful alerts appearing every day point to a workflow problem.
The hidden cost of constant replacement
Replacing a seat does not immediately replace operational knowledge. Experienced analysts know how systems normally behave, who owns critical assets and what previous incidents revealed. New colleagues need time to develop that context, while senior analysts need time to support them. Review departures alongside overtime, investigation backlogs, escalation delays and time to independent working. Recruitment can restore capacity; it cannot, by itself, repair unsustainable working conditions.
Improve the queue before expanding the team
Review detection rules for repeated false positives, duplicate alerts and missing business context. Give detection tuning a named owner and protected time. Test changes against relevant threats and document their effect on coverage. A quieter queue is valuable only when detection remains effective. Closing or suppressing more alerts should never become a substitute for understanding risk.
Build coverage around the work
Complex investigation, initial triage and incident coordination require different levels of effort. Leave, training, handovers and incident surges also need capacity. NIST places incident response within organisation-wide risk management; the SOC should not be expected to carry every responsibility alone.
- Define ownership for triage, deeper investigation and incident coordination.
- Make senior support and escalation routes clear on every shift.
- Agree which actions analysts can take independently and which need approval.
- Plan handovers with IT, engineering and business teams, including out-of-hours support.
Hire for judgement—and describe the job honestly
Use a short, realistic exercise with incomplete evidence. Ask what the candidate would check next, what remains uncertain and when they would seek help. Look for sound reasoning, clear documentation and proportionate escalation. Explain shifts, on-call expectations, mentoring and actual responsibilities before making an offer. A role advertised as threat hunting should not turn out to be exclusively queue clearance.
Give automation a defined purpose
Automation can gather context, group related alerts and prepare investigation notes. AI is not an automatic solution to staffing pressure: IBM cautions that agents working with poor-quality raw telemetry can reproduce the underlying noise problem. Start with a bounded task and check whether the output helps analysts. Keep source evidence accessible and actions traceable. Set approval requirements for high-impact actions, such as disabling accounts or isolating systems, according to the organisation’s risk and response procedures.
Make development part of the working week
Protect time for case reviews, detection improvements, mentoring and supervised investigations. Explain progression into incident response, detection engineering, threat intelligence or cloud security where these routes exist. Define the capabilities a person needs, how they can demonstrate them and what support is available. Career development should offer more than responsibility for a larger queue.
Measure sustainable performance
Alert closure counts and average handling time tell only part of the story. Use measures to identify operating problems rather than create pressure to close cases prematurely.
- Track backlog age and high-priority investigation delays.
- Review duplicate alerts, false positives and reopened cases.
- Assess documentation quality and the usefulness of escalations.
- Review overtime, leave coverage and protected training time.
- Listen to analyst feedback and examine the reasons people leave.
Start with the next 30 days
Talk to analysts across shifts and sample repetitive alerts and delayed investigations. Identify one recurring noise source, one coverage gap and one escalation bottleneck. Assign owners, make limited changes and review the effect on investigation quality and workload. A resilient SOC is not a team that endures unlimited pressure. It is an operating model designed to support sound judgement over time.
Build the team around the work
Before hiring, define the capabilities, coverage and responsibilities the team needs. Clear role design helps candidates understand the opportunity and gives managers a more useful basis for selection. Discuss your cybersecurity hiring requirements with ULTISOURCE, starting with the work your team needs to deliver.
References & further reading
This guide offers practical evaluation questions. The sources below provide the underlying risk-management and assessment principles; they do not endorse ULTISOURCE or its products.
