How a Five-Analyst MSSP Increased SOC Capacity by 25% with Threat Intelligence

Blog WriterCybersecurity News - Original News Source is cybersecuritynews.com


Every managed security service provider eventually hits the same wall. New clients bring more endpoints, more log sources and more alerts, while SLAs get tighter and qualified analysts stay expensive and hard to hire. The obvious fix is headcount. 

A US-based MSSP with one SOC manager and five analysts chose a different route: it changed how its team gets threat context, and ended up handling about 30% more alerts with the same people.

This article walks through what that MSSP changed, why MSSP threat intelligence matters more for providers than for single-company SOCs, and what other service providers can take from the approach.

The problem: growth that outpaces the team

The provider, which asked to remain anonymous, serves a growing list of customers, including enterprises with thousands of endpoints.

As the client base expanded, three pressures arrived together: rising alert volume, stricter SLA commitments and pressure on staffing costs.

Its investigation workflow was typical of many mid-sized MSSPs. Alerts were enriched inside the SIEM, and analysts then checked suspicious indicators against open-source IOC sources by hand.

That works at low volume. At higher volume, every unfamiliar domain, hash or IP address turns into a small research task, and those tasks pile up across clients.

The team considered hiring. As the company’s Head of SOC put it, “Hiring more analysts was one option, but we also wanted to improve the way we worked.”

The real question was whether some of the threats the analysts were researching could have been recognized earlier, before anyone spent time on them.

Why MSSPs feel the context gap harder

An in-house SOC defends one environment and learns its normal behavior over time. An MSSP defends many environments at once, each with different software, users and risk.

The same suspicious file might appear at three clients in a week, and without shared, current intelligence, three analysts may each investigate it from scratch.

This is where threat intelligence earns its cost for a provider. Fresh, verified indicators let the SOC recognize known-bad activity on arrival.

Rich context (which malware family, which campaign, which infrastructure) lets analysts decide quickly whether an alert matters. Both reduce the number of alerts that need full manual research, which is the most expensive work a SOC does.

Give your MSSP earlier visibility into up to 30% of unique malicious IOCs and strengthen detection without adding manual research.Protect More Clients with Less Work

Step 1: sandbox analysis built into the SOC workflow

Explore geo and industry context by browsing Threat Intelligence Lookup in natural language

The MSSP’s adoption happened in stages, which is part of why it worked. Analysts first used the ANY.RUN Interactive Sandbox individually to detonate suspicious files and URLs and watch their behavior.

After several months, the company moved to an enterprise plan and connected the sandbox to its SIEM through the API, so analysis became part of the standard investigation path rather than an ad hoc tool.

Behavioral analysis answers the question static indicators cannot: what does this sample actually do? For a provider, getting that answer in minutes instead of hours across many clients is a direct gain in capacity.

Step 2: threat intelligence feeds that catch threats on arrival

Threat Intelligence Feeds by ANY.RUN deliver IOCs from live sandbox analyses into your security stack

About six months after the sandbox rollout, the MSSP added ANY.RUN Threat Intelligence Feeds and connected them to the SIEM through an out-of-the-box integration. Indicators that matched the feed were tagged as malicious automatically.

That change moved part of the work from investigation to detection. Instead of an analyst opening an alert, pulling an IOC and researching it, a known-malicious indicator arrived already labeled. 

According to ANY.RUN’s own analysis of sandbox sessions, around 30% of unique malicious IOCs were already present in its feeds before they were investigated, which shows how much research time early visibility can remove.

The feeds draw on sandbox activity from what the company says are more than 16,000 SOCs and 700,000 security professionals.

Step 3: lookup for the alerts that still need a human

Why MSSP companies choose ANY.RUN solutions

Feeds cover what is already known. For everything else, the team added Threat Intelligence Lookup, which analysts use manually to research indicators, connected infrastructure and related activity across industries. 

When an alert does not match a feed, the analyst can quickly see whether a domain or hash has appeared in other attacks, which malware it relates to and what else belongs to the same campaign.

This gave the SOC a consistent research method across all customer environments, rather than leaving each analyst to assemble context from scattered open sources.

The results: more alerts, same team

Once all three pieces were in place, the provider reported:

  • About 30% more alerts handled with the same five analysts. “We were handling around 30% more alerts with the same team,” the Head of SOC said.
  • 25% greater SOC capacity, which the company could use to take on more clients without immediately adding staff.
  • Easier SLA compliance, because fewer alerts stalled waiting for manual research.
  • Less time per alert and fewer manual checks, as feed matches and sandbox verdicts replaced repetitive lookups.

The business effect matters as much as the operational one. For an MSSP, capacity is revenue. Freeing a quarter of the team’s capacity is roughly the output of an extra analyst, gained without the cost and ramp-up time of a new hire.

Cut response time by up to 21 minutes with context-rich threat intelligence while keeping your MSSP’s investigation costs under control.Boost Your MSSP’s Efficiency

Lessons for other MSSPs

  1. Measure where analyst time goes. Track how many alerts need manual IOC research and how long that takes. That number shows how much a feed or lookup service could save.
  2. Integrate, do not just subscribe. Intelligence that lives in a separate portal still costs analyst time. Push feeds into the SIEM or SOAR so matches are tagged automatically.
  3. Roll out in stages. This MSSP proved value with the sandbox first, then added feeds, then lookup. Each step was easier to justify with results from the previous one.
  4. Standardize research across clients. A shared lookup method gives every customer the same triage quality, regardless of which analyst is on shift.
  5. Tie the metrics to the business. Report capacity and SLA results in terms leadership understands: clients served per analyst and cost per investigation.

How ANY.RUN helps MSSPs scale

The approach in this story is built on three ANY.RUN products that work together. The Interactive Sandbox shows how a file or URL behaves in a live environment, so analysts reach a verdict quickly.

Threat Intelligence Feeds deliver fresh, verified IOCs from real sandbox analysis straight into the SIEM, catching known threats before an analyst touches them.

Threat Intelligence Lookup provides deep context for the indicators that still need investigation.

ANY.RUN says more than 2,170 MSSPs already use its services. For a provider facing the same squeeze between growth and headcount, the practical starting point is to connect the feeds to the existing stack and measure how many alerts arrive already resolved.

Integrate TI Feeds into your existing security stack to close detection gaps and protect more clients.Expand Detection Coverage

The post How a Five-Analyst MSSP Increased SOC Capacity by 25% with Threat Intelligence appeared first on Cyber Security News.