SolutionsPricingWorkshopsBlogNewsAboutLet's Talk

Gartner: SOCs to have 50% more engineers than analysts by 2028

AI agents already handle routine alert triage. The report recommends shifting analysts to full case ownership. Implications for hiring and system design.

AutomushPublished 2 min readSource: BleepingComputer

A 2026 Gartner report by analyst Pete Shoard predicts that by 2028, security operations teams will have 50% more engineers than analysts. The report finds that SOC AI agents already significantly reduce alert-handling work for traditional and common use cases.

What is actually happening

The report recommends that human analysts shift from alert triage roles to end-to-end ownership of cases and effective communication of response options. This shift is not future-tense – AI agents already handle common use cases, and the question is how to organise the team around the new capabilities.

This structural change reflects a simple reality: when an AI system filters and handles 80% of alerts, the remaining job is not to review more alerts but to build better processes, communicate with business units, and understand how to improve the system itself. That requires engineering skills, not analytical ones.

Why it matters beyond the headline

Israeli companies building or operating security systems need to understand that the organisational structure of information security is changing fundamentally. The shift from alert handling to case ownership changes skill requirements and hiring processes.

It also affects decisions about building internal capabilities versus buying external services. A managed security provider still relying on a large team of analysts will be more expensive and slower than one that has already built automations and employs engineers who know how to improve them.

Long-term planning for security teams must account for the fact that the skills required today are fundamentally different. An analyst who can read logs does not necessarily know how to build an automated workflow or communicate response options to managers.

What to do this week

If you operate an internal security team, check how much time your analysts spend on manual alert filtering. If it is more than 30% of their time, there is a gap you can close with simple automation before hiring more analysts.

If you buy external security services, ask the provider how they handle common alerts and what their automated handling percentage is. A vague answer or an explanation about “experts reviewing every case” is a sign the provider has not yet made the shift.

If you are considering building new capabilities, start with one repeating process – for example, handling suspicious login attempts or scanning uploaded files. Build an automation that handles simple cases and escalates only real exceptions for human review. This will quickly show you whether you have the right skills on the team. For more on building controlled automated processes, see managed automation solutions.

Sources

Frequently asked questions

Should we replace existing analysts with engineers?

No. Good analysts can transition to case ownership and communication roles with business units, which require deep understanding of threats. The question is what skills to add in the next hires, not who to fire.

How long does it take to build automation that replaces analyst work?

A single repeating process – for example, handling one type of alert – can be built and deployed to production in two weeks to a month. Full coverage of common use cases typically takes three to six months, depending on environment complexity.

Related guides

To the blog

Which of your processes could run on its own?

A free 30-minute discovery call, no commitment. We map your processes together and tell you honestly whether and how automation can help.

Try a call with agent now