How to Improve SOC Efficiency with AI
SOC continuous improvement fails when insights get buried in closed tickets. Learn a 6-step LLM pipeline that allows your SOC to use AI to turn investigation notes into action.

I was there, I sat in every SOC seat out there…
A SOC analyst grinding through alert queues at 2am. Part of an Incident Response team leading running war rooms. A SOC manager in Monday morning stand-ups asking what we learned this week while staring at blank faces.
Learn more about how Virgin Money’s SOC used Legion Security’s AI to improve their SOC’s efficiency.
The insights, recommendations, self improvement, the de-facto SOC continuous efficiency improvement action items were disappearing. Seating documented in a case log for no one to action upon, trapped inside closed tickets that live in a backlog nobody rarely reopens.
I know the why and I feel the overwhelming operations, which is why I’m offering a practical solution for how to improve SOC efficiency with AI by turning the insights from your investigations into continuous improvements.
The Hidden SOC Efficiency Goldmine You're Sitting On
Every ticket your team closes tells a story. It's not just that an alert fired, then an analyst investigated and eventually closed. There are powerful signals buried in those notes, whether it's a tool with overly noisy alerts, a gap in your email gateway rules, or the same user clicking a phishing link for the third month in a row.
Your tier 1 all the way to your tier 5 analysts and IR responders are generating intelligence every single shift and with every single incident. They know things and they're writing them down. It's useful information but these notes get buried and never read again.
It's a sad truth... I know because I've been in those weekly SOC meetings, I was running them.
It's not a people problem, rather, it's a system problem.
The Weekly Report Trap
The thing people look to as the standard fix is the weekly report. In theory it's elegant: senior analysts summarize the week, extract the learnings, feed them back into tier 1 runbooks and detection improvements. On paper, it's a proper feedback loop.
In practice, it becomes the task that either gets rushed on Friday afternoon or simply doesn't happen. It's for good reason too! Your senior analysts are already stretched because on top of everything they need to do for their jobs, they're also being asked to synthesize everything in themes. You either get a half-hearted copy-paste of ticket titles, or, more likely, you get nothing.
Teams try rotation where everyone takes a turn on the ferris wheel. But in doing so, you face losing important insights and information, not to mention a lack of consistency.
Now add a follow-the-sun operation to this. APAC closes tickets while EMEA is asleep. EMEA handles incidents while Americas is offline. By the time anyone tries to compile a summary, they're working with fragments. Nobody has the full picture. The patterns that only emerge when you look across all shifts stay invisible.
Can AI Improve SOC Efficiency?
When capable LLMs became available, I thought we finally had an easy way to improve SOC efficiency with AI. Just feed all the investigation summaries in, ask for a weekly report. Done? Not so fast... here's what actually happened.
First attempt: I gave the best LLM models that money can buy more than 250 investigation summaries and asked for a consolidated report. But what I got back was a mess.
What I saw were recommendations repeated five times just with slightly different wording. Severity assessments that made no sense and my “favorite” recommendations that are not feasible, for example “Tune your EDR machine learning to reduce false positives of macro xlsx files”.
No traceability whatsoever, no way to tie anything back to the original investigation and forget about cross referencing with similar recommendations.
Second attempt: I went deep on prompt engineering. Longer prompts. More detailed. With examples. The results improved marginally, but the ceiling was surprisingly low.
The fundamental issue is that when you dump a large context with complex requirements into a single LLM call, it can't hold everything in working memory. It forgets constraints from earlier in the prompt. It hallucinates connections between unrelated incidents. Severity levels come out inconsistent.
One-shot approaches get you mediocre fast. They don't get you useful.
The Breakthrough: Think Multi-Step, Not Prompt
The shift that changed everything was stopping thinking about this as one task and starting to think about it as a multi-step pipeline.
When an experienced analyst writes a weekly report, they don't try to do it all at once. They read, they group, they prioritize, they write. Multiple steps. Each one is different.
So I built it that way.
The 6-step SOC AI improvement pipeline
The result is a six-step approach that uses AI to improve SOC efficiency without asking analysts to change how they already investigate or document incidents.
Step 1: Classification
The first step does one thing and one thing only. It extracts and categorizes recommendations from raw investigation summaries. It looks for whatever your analysts call them: Recommendations, Do Better, Action Items, Next Steps. It pulls each one out and assigns it to a category: detection, prevention and process improvements.
No dedupe. No severity. Just extraction, done well.
Step 2: Feasibility Assessment
Now we evaluate each recommendation against practical reality. Can this actually be implemented? Is it a quick win or a multi-quarter project? Does it require resources you don't have?
This is also where web search earns its keep. When a recommendation references a specific product or vendor, the model can look up current best practices, product documentations, tech community discussions and verify the suggested configuration actually exists and is supported. Without this, you get generic, often infeasible advice. With it, you get grounded recommendations.
Make sure to use an LLM model that has web search capability via API calls.
Step 3: Citation Attachment
Before touching deduplication, every recommendation gets linked back to its source investigation. This is non-negotiable for a report anyone will actually act on. When a SOC manager reads and SOC teams attempt recommendation implementation, they need to know which investigations triggered that and value with volume justification to it. Otherwise it's just noise or worse, it might break business operations.
Step 4: Deduplication
Three analysts working three separate investigations but same use case, all recommend the same prevention improvement. Without deduplication, you get three entries saying the same thing with slightly different wording. With it, you get one consolidated recommendation that shows it came from three independent investigations, which is actually a stronger signal.
Citations from all source recommendations get merged. Nothing is lost.
Step 5: Severity Classification
Now, with duplicates consolidated, we can assign severity levels that actually mean something. The model evaluates security impact per your instructions, weights and SOC defined severities for each use case. Not how urgent did the analyst feel when writing this, but what is the actual risk if this doesn't get addressed built on your SOC knowledge base.
Separating this from extraction forces objectivity. If you try to assign severity while also pulling recommendations from raw notes, the analyst's tone bleeds in and skews the assessment.
Step 6: Report Generation
Everything feeds into the final structure. The model has category breakdown, feasibility assessments, severity levels, citation references. It produces a coherent report with an executive summary and recommendations sorted by severity, with enough context to actually act on. Also comparing recommendations week on week to get remediation/implementation progress for repeated action items.
Add another layer of disregard recommendations and you have a magnificent mechanism.
No LLM at this stage, actually. It's programmatic and deterministic. It assigns citation letters for easy grounding and reference of recommendation with feasibility (A, B, C...), builds the reasoning section for each recommendation, and outputs clean JSON ready for whatever you want to do with it.
Why This Approach Improves SOC Efficiency
The goal is to achieve focused context at each step. Instead of one massive prompt juggling ten objectives, each step gets only what it needs. Fewer constraints to forget.
Modular iteration is the name of the game here. When severity ratings were inconsistent, I refined only the severity prompt. When analysts switched from Recommendations to Do Better as their section header, I updated only the classification step and nothing else broke.
Inspectable intermediate outputs. Between every step, results are saved. If something looks wrong in the final report, you can trace back through the pipeline and find exactly where it broke. Debugging is possible, which is not nothing.
Web search in the right place. Not as a general capability, but specifically in the feasibility step where it does the most work. Validating that a recommended configuration actually exists changes the quality of the output completely.
The Payoff
This is where using AI to improve SOC efficiency starts to pay off. Your analysts don't change anything, they can run the same investigations, keep the same ticket notes they're already writing. The pipeline simply runs against their existing documentation.
The output is consistent. Same structure, same categories, same severity criteria, every week. You can compare week over week and actually spot trends. You can see if the same recommendations keep surfacing, which means they're not getting actioned, which is itself a signal.
The feedback loop that should have existed closes automatically. Tier 2 findings reach tier 1. Detection gaps surface. The Monday morning question about what we learned has an answer.
Build it or use it
Building this right takes time. Getting prompts tuned for the variety in how analysts write, handling edge cases, making it robust across different ticketing systems. It's not weekend work.
If you want to build it yourself: start with extraction only. Get that reliable first. Then add deduplication. Then severity. Don't try to build the whole thing at once.
If you're looking for how to improve SOC efficiency with AI without building this pipeline yourself, this is exactly what we built at Legion Security. Already tuned across real SOC environments, connected to your existing ticketing system, your analysts change nothing.
Either way: stop burying the intelligence your team generates every day.
Your team is learning constantly. Those lessons deserve to surface.
Written by someone who's been the analyst, the IR lead, and the manager staring at the empty Monday morning whiteboard.
Every security team is told to know its adversaries, but for the analysts on the front lines, threat intelligence rarely arrives as known information. Turning feeds, vendor advisories, headlines, or a frantic message from an exec into a confident answer about real risk to the enterprise is (one of many of) the hard parts, and it's where a lot of the work (and frustration) lives for security professionals.
In this piece, I’ll aim to look at why that gap persists, what it looks like during a real incident, and how we think agents and analysts can close it together.
Why threat intelligence is so hard to act on
Threat intelligence comes in layers, and each one decays at a different speed. Indicators of compromise like hashes, IPs, and domains can be among the easiest to consume, but attackers rotate them constantly. Tactics and techniques last longer, but they're harder to engineer into a detection rule because they describe behavior rather than a specific artifact you can search for. Emerging campaigns (PHP, anyone?) sit on top of both, mixing new infrastructure with familiar techniques in ways that rarely match what the detection stack was built to catch.
The real challenge is relevance and translation to the different stakeholders across an enterprise. While a feed can tell you that a group is exploiting a specific vulnerability, it can't tell you whether you run the affected software, whether it's exposed, whether anyone has already touched it, or what it connects to. Analysts fill that gap by hand, pivoting across the SIEM, EDR, asset inventory, vulnerability scanner, and cloud console, and that work competes with an alert queue that never stops. And now, as attackers use AI to operate at greater scale and speed, that backlog grows faster than any team can possibly manage by hand.
What the recent PHP incident looked like from the inside
The recent PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619 shows how this plays out. The advisory came out, proof-of-concept code followed quickly, and within hours security teams everywhere were asking and being asked… How exposed are we?
Answering this type of question is rarely one query. Security pros first had to find every system running PHP, including the affected versions and configurations, which usually means reconciling an outdated asset inventory with scanner results that are only as fresh as the last scan. Then they have to work out which systems are internet-facing, which typically sit behind a WAF, and are owned by teams that security likely doesn't talk to every day. Homegrown applications and legacy servers are the hardest, because they often live outside the tools that would report them.
From there, the work splits into parallel tracks. Threat hunters search logs and endpoint telemetry for signs of exploitation using whatever indicators have been published. Detection engineers write and tune new rules. Vulnerability management chases patch owners and tracks exceptions. Each track lives in a different tool with a different owner and cadence, and the whole process has to keep firing as new indicators and exploit variants appear over the following days. Most teams hold it together with tickets, spreadsheets, and a lot of Slack messages, if at all. And it’s not even their fault! Especially in a crisis, if something is confidently labeled as an endpoint issue but it really is an identity problem, it’s very easy to get skipped over, marked as benign, or not correlated / communicated to other departments. It’s just full-steam ahead.
Then comes the question from the top
While all of that is happening, the security analyst needs an answer for the CISO, who needs an answer for the CEO, who in turn needs one for the board. Leadership doesn't have much use for a list of hosts, they want to know whether the business is at risk, what was exposed, whether anything was compromised, and when the problem will be closed.
Assembling that answer means stitching together findings from every parallel track, each with its own definitions and level of confidence. The analyst summarizes for the security manager, who summarizes for the CISO, who translates it again into business terms for the executive team. Every hop loses detail and adds delay, and by the time the summary reaches the board, the facts underneath it have often changed. Security leaders end up reporting effort, like patches applied and rules written, because measuring actual risk reduction quickly is so hard.
How agents and analysts could (should?) share the work
At Legion, we believe the answer isn't yet another feed or another dashboard, but rather it’s a coordinated set of agents (some may call this a legion) that handles the repetitive, cross-tool work of threat intelligence alongside the analysts who own the judgment calls.
In practice, that means agents that operate the tools your team already uses, through APIs and MCP, and through the browser for homegrown and legacy systems that have neither. When a new threat lands, agents can find affected assets, check exposure, hunt for indicators and techniques across telemetry, and enrich every related alert with that context, so scattered signals become a single case. Because agents investigate every signal rather than just the top of the queue, they catch attacker activity that's spread thin across many low-priority alerts. This is one of the many use cases that our customers are using DragonClaw for in production today.
Those agents should also learn how your team really works. In a crisis, analysts rarely have time to open the runbook or follow every step to a T. They act on a hunch from a similar case last year, skip the query they know will come back empty, or already know which detail the CISO will ask about first and pull it before anyone asks. That instinct is some of the most valuable knowledge in a security enterprise. When agents learn from recorded investigations and the decisions analysts actually make under pressure, they capture those shortcuts too, so the next incident moves at the speed of your best analyst's instincts where those are the right path, and creates new, optimal paths for others.
From headline to boardroom
I don’t believe it’s ambulance chasing, but rather a known fact to suggest that the next incident like this one is already coming. From what we see, the teams that handle it well will be the ones who can move from headline to exposure to action to a clear executive answer in hours instead of days. That's the shift we're building, agents that carry the cross-tool work at machine speed, and analysts who spend their time on the decisions that actually reduce risk.

Using the recent PHP vulnerabilities as an example, see why threat intel is so hard to act on and how agents and analysts can close the gap together.
TL;DR: DLP tools generate more alerts than analysts can properly investigate, so many get closed based on whatever the alert shows. DLP alert automation cuts DLP alert fatigue by taking on the work that comes after an alert fires. Legion learns how your team investigates, gathers context from across your systems and applies that approach to every alert.
DLP alert fatigue (why DLP alerts are everywhere)
You already know that DLP is one of the noisiest sources of alerts. DLP alerts fire whenever a user performs an activity that matches the criteria of a rule in a DLP policy, and the organization has incident reporting configured to turn those matches into alerts. Every email, file share, upload, print job and USB copy is a chance for a rule to match, so in an organization of any real scale, the alerts Never. Stop. Coming.
Each of those alerts asks the analyst the same underlying questions: Did sensitive data actually leave the organization, or was it about to go somewhere it shouldn't? If it did, was that an honest mistake, a legitimate business action, or something malicious?
Answering those questions accurately requires a genuine investigation, but when dealing with a noisy alert cannon, not every alert is able to be properly investigated, resulting in a ton of false-positives, analyst burnout, and potentially even false-negatives. That’s where DLP alert automation comes in.
What is DLP alert automation?
DLP alert automation means using automated tools to do some or all of the work after a DLP alert fires. That includes pulling context, looking at the content that matched, deciding whether it’s a real risk and acting on it.
There are two main approaches to DLP alert automation.
- Rule-based automation, such as SOAR playbooks, follows predefined workflows. It can enrich alerts and take actions like opening a ticket or disabling an account, but only along paths someone has configured in advance.
- Agentic tools work through each alert the way an analyst would, reach a verdict and pass the high-risk or unclear cases to a person.
What a DLP investigation actually looks like
The details vary from one DLP platform to another and from one organization to another, but the shape of the investigation is mostly consistent.
- Find the alert
- Read what triggered it
- Look at the destination and the action
- Review the content itself
- Add user context
- Decide and act
- Tune the policy
Whether any of these steps actually presents a risk depends on information most DLP tools in isolation don’t have, because it’s scattered across the enterprise. Identity data sits in your IdP, device posture sits in your EDR, employment status and upcoming departures sit in your HR system, and the history of what this person normally does is spread across months of logs and cases in several different places.
Some of it may not even be available at the moment the alert is being reviewed, so the analyst is left with two imperfect choices.
- They can investigate the alert fully, pivoting between various consoles to assemble the full picture → which stalls the investigation while the queue keeps growing
- Perhaps more frequently, they make the call based on whatever the DLP alert shows them → likely the alert gets closed as a false positive or benign business activity because nothing in front of them suggests otherwise
Most organizations have already invested heavily in DLP. Their teams have spent years writing policies, defining sensitive information types, mapping where regulated data lives and deciding which activities should trigger an alert. What’s missing is everything that happens after the alert fires.
Every organization investigates DLP alerts a little differently, shaped by its own processes, tools and people. Some teams have a well-honed approach built up over years, while others are still working out what a good investigation should look like, and most are somewhere in between.
Legion meets you wherever you are. It learns how your team already looks into DLP alerts and signals, then helps fill the gaps and refine the process as it sees what works, and carries it out consistently on every alert at machine speed from alert through response and remediation.
How Legion automates DLP alert investigations
When an alert fires, Legion reads the policy and rule that matched, looks at the destination and the action, checks the content, and then goes out to gather the context that the DLP tool can't provide on its own.
To investigate DLP properly, security analysts (or their agentic counterparts) need cross-system context. They also need the context of your business itself, meaning your trusted partner domains, your sanctioned storage locations, the teams that routinely handle regulated data, and the people who need to hear about a confirmed incident. None of that lives inside the DLP tool, which is precisely why a DLP-only approach struggles and why Legion is designed to connect to the systems where that context actually lives, whether they have clean APIs or not.

This is also what changes the value of the DLP tool itself. On its own, a DLP platform is very good at seeing things like where and when sensitive data is moving, and telling you which rule it matched, but it has no way to judge whether that matters.
When Legion operates the DLP tool, opening the alert, reviewing the matched content, and taking actions inside the console such as revoking a sharing link or applying a label, that DLP tool (or tools) effectively gains an advanced-level brain. Every detection now arrives with the identity, endpoint, HR and business context needed to make a decision, and every decision can be acted on right where the data lives.
The policies your team has spent years building finally get the judgment they were always missing, so the DLP investment starts producing answers instead of just alerts. For situations where a rule keeps generating the same false positive, that pattern is visible, so tuning the policy becomes a decision rather than a guess.
Because Legion learns, understands, and optimizes your team's logic rather than implementing a generic playbook, its conclusions look like the ones your *perfect* analyst would reach.
Your expertise, at the scale of your alert queue
DLP alerts aren't going to slow down, and we shouldn't expect them to. In fact, we should all expect them to pick up. The real problem has always been that a thorough investigation depends on context spread across a half-dozen tools and on judgment that lives with a few experienced people on your team.
Legion brings DLP alert automation to the processes your team already follows. It learns how your organization investigates DLP, connects to the identity, endpoint, HR and business context that the DLP tool can't see, and applies the optimal approach to every alert in the queue.
Your analysts get their time back for the cases that genuinely need a human, and every DLP alert gets the investigation the perfect analyst would give it.

Legion brings DLP alert automation to your existing tools, adding the context and judgment needed to investigate every alert, identify real threats, and take action.
Legion’s agentic security platform is built on a simple idea: your team knows how to investigate, but it is knowledge that is one of the most valuable and unique things your SOC has. Legion captures how your analysts work, all the way from an alert, to the steps they take to the evidence they gather and the reasoning behind each verdict, and turns it into agentic investigations that run the same way every time.
But that context should not stay locked inside a single console for knowing analysts. Security teams increasingly do their thinking in AI assistants like Claude and ChatGPT, whether they're drafting an incident summary, preparing for a leadership update or trying to remember whether they've seen an indicator before. That's why we offer our customers the Legion MCP server, which connects those assistants directly to your Legion data through the Model Context Protocol. With this, security teams can ask questions about their investigations in plain language, from the tools they already use every day, and get answers grounded in what Legion actually did.
What your team can ask
Once Legion is connected, an analyst or security leader can pull up the full story of an investigation without leaving their conversation. They can find sessions by title, summary or entity, filter them by status, decision, workflow, analyst or date, and walk through each step along with the verdict it reached. They can also see which workflows and use cases are running, check how much of their monthly action allowance has gone to guided versus autonomous runs, and get answers about Legion itself from our documentation, with links back to the source pages.
In practice, that means questions like these:
- "Summarize our Legion sessions from the last 24 hours: what failed, what's still active, and which were decided true positive."
- "Open our most recent phishing investigation and walk me through each step, the entities it found, and why it reached its verdict."
- "Have we investigated 203.0.113.42 before? List every session that mentions it, with dates and outcomes."
- "Which workflows ran most last month, and what use case does each belong to?"
- "How close are we to our action limit this month? Split it by guided and autonomous runs."
- "How do I set up a Jira poller so new tickets trigger a workflow? Cite the docs."
Because the answers come from your own investigations, the assistant isn't guessing at how your SOC handles an alert. It's reporting what your team's process actually found, which makes it far more useful for shift handoffs, executive briefings and the everyday question of "have we seen this before?"
Built with security teams in mind
We know that connecting security data to an AI assistant raises fair questions, which is why our MCP server starts by being conservative, gaining your trust as it goes. It's read-only, which means it can't create, change or delete anything in Legion, and it can't run workflows, skills or agents. Each person connects from their own assistant and signs in with their own Legion account, so every request runs as that user and is checked against their Legion role. Nobody sees more through Claude or ChatGPT than they could already see in Legion.
Admins stay in as much control as they want, throughout deployments. MCP access is turned off until an admin enables it for the organization, and it can be switched off again at any time. Individual users can disconnect Legion from their assistant whenever they like, and admins can revoke a specific user's sessions, which ends that person's MCP access within about a minute.
Getting started
Setup takes just a few minutes. Legion has always been about capturing the way your team investigates so that expertise can scale. With MCP, that expertise travels with your team, into the assistants where more and more of their work already happens. If you’d like help in configuring this or to learn more, please reach out to [email protected].

Connect Claude and ChatGPT to Legion via MCP and ask about your investigations in plain language, with read-only access scoped to each user’s role


