Threat-Led Security Operations

Written by: 
Rafał Kitab
Published on: 
Nov 17, 2026
On This Page
Share:

We don't suffer from a lack of threat detection content. I'd argue we never have.

From mountains of community-written detections, tools shipping with thousands of out-of-the-box rules and now AI writing detections (quality aside), we can safely say that the volume problem is solved. Training is accessible too - there are numerous courses on how to threat hunt, write detections and respond to security alerts.

All of this is to say that the success of your security monitoring program is not about whether you'll find the right detections or competent staff, because you likely will. What will end up determining your success is how well you use your finite resources and prioritize which threats get detected and acted upon.

The tale of two constraints

Talk to enough SOC leaders and you'll hear two complaints - the SIEM is too expensive, and there are too many alerts to deal with. Those two issues often stem from a single problem: the lack of a security monitoring strategy, or rather falling into one of two common anti-patterns:

  • Collecting too much data
  • Alerting on too many things

And that's completely fair - after all, it does make sense to collect everything that's remotely security relevant and alert on all suspicious activity. The issue is that this only works for organizations with infinite security budgets.

There are no such organizations.

Security budgets are typically around 1% of an organization's revenue, or approximately 10% of the IT budget. And even generous budgets don't guarantee that analysts can handle the alert volume they're presented with. After all, to know when your team's work capacity is reached, you need a way to measure it.

The two main constraints you work against as a SOC leader are your budget and your team's work capacity, especially where alert handling is concerned. It means you have to prioritize.

How Abstract helps you prioritize

SIEMs have traditionally supplied a blank security data analytics platform and left users to figure things out themselves. At Abstract we aim to tailor the experience for you to deliver an effective platform out of the box. We believe SIEM success is equal parts process and technology and it is our job to bridge the two for our clients. We do that by building a threat profile.

It all starts with our threat research team.

ASTRO (Abstract Security Threat Research Organization) researches threat actors likely to target our your organization. We observe which techniques those actors are known to use and outline a list of most likely threats to materialize in your environment.

From there we work with you to add your context to the model. Your crown jewels, past incidents, IT / OT stack, VIPs, CMDB and more. The model gets more accurate the longer we work together, and the targets move as the threat landscape moves.

Detections are planned against those detection targets. Each one comes with the data it needs to run and the data an analyst needs to investigate it when it fires. That defines what goes into the SIEM. The pipeline handles the rest: compliance data goes to archive, context data goes to cheaper long-term storage, and data nobody uses gets dropped before you pay to store it.

What you end up with is a program you can explain. One that starts with threat research and uses it to map threat detection targets, which then inform data onboarding needs.

‍From intelligence to a security monitoring strategy.

Written by:
Rafał Kitab
BUILD YOUR THREAT PROFILE
THREAT PROFILER
GET
‍ABSTRACTED

We would love you to be a part of the journey, lets grab a coffee, have a chat, and set up a demo!

‍

Your friends at Abstract AKA one of the most fun teams in cyber ;)

White light beam passing through a black circle with a pink abstract symbol, dispersing into multicolored beams on the right.
Thank you!
Your submission has been received.
Oops! Something went wrong while submitting the form.