Blog Attacks at machine speed
Blog · Threat landscape
Attacks at machine speed: why human-paced triage can’t keep up
For years, defenders could assume that an intrusion would take days to unfold. Public research now shows attackers moving in minutes. This article looks at what has changed, why the traditional alert queue cannot absorb it, and what a security operation built for this pace looks like.
The clock has changed
Breakout time is the window between an attacker’s first foothold and their first move to another system. It matters because it is the defender’s best chance: stop an intrusion before it spreads, and it stays a contained incident rather than a company-wide breach.
That window has collapsed. CrowdStrike reports that the average eCrime breakout time fell to 29 minutes in 2025, with the fastest breakout it observed taking 27 seconds. In one intrusion, data exfiltration began within four minutes of initial access [1]. The same report notes an 89% year-over-year increase in operations by AI-enabled adversaries [1]. Automation and AI tooling let one operator run many intrusions in parallel, script the reconnaissance, and move as soon as a door opens.
Exploitation follows disclosure faster every year
The second clock is the one that starts when a vulnerability becomes known. Mandiant tracks the average time to exploit: it was 63 days in 2018-2019, 44 days in 2020 to early 2021, 32 days across 2021-2022 and just five days in 2023 [2]. Many of the vulnerabilities exploited are zero-days, abused before a patch exists at all.
Breach data points the same way. Verizon reports that exploitation of vulnerabilities as an initial access step grew by 34% and now accounts for 20% of breaches [3]. Mandiant’s M-Trends 2025 lists exploits as the most common initial infection vector for yet another year, at 33% [4]. Patch cycles measured in weeks, and change windows measured in months, are now longer than the attacker’s timeline.
Where a human-paced queue loses time
Follow one alert through a typical SOC and the delays add up long before anyone acts.
01
Waiting
The alert joins a queue of hundreds. Its position depends on a severity field written by a rule author, not on what is happening right now.
02
Opening and context
An analyst opens it, then looks up the host, the account, recent logins and what the machine normally does, often across several consoles.
03
Correlation
The analyst searches for related alerts. Pieces of the same intrusion sit in other tickets, sometimes with other analysts.
04
Escalation
A Tier-1 analyst escalates to Tier 2, who repeats part of the work and asks for more evidence.
05
Decision and action
Someone with authority decides to contain. The change request goes to another team that owns the EDR or firewall.
More people do not change the shape of the problem
Each step above is reasonable. Together they take hours, and on a busy night far longer. Adding analysts shortens the queue a little but leaves every step in place, and the attacker’s cycle is now shorter than the time it takes to read the alert, gather context and agree on a decision.
There is also a mismatch of shape. Attackers work on a story: a phishing click, a credential, a new process, a connection to a server, a copy of data. SOC tooling usually delivers those pieces as separate alerts, each with its own severity, often to different people. The work of reassembling the story is exactly the work that takes the most time.
Speed also pays off in money. IBM’s 2025 study puts the average time to identify and contain a breach at 241 days, and finds that organisations using AI and automation extensively in security shortened that lifecycle by 80 days and saved an average of USD 1.9 million [5]. Faster is not only safer; it is cheaper.
What a machine-speed SOC needs
Matching the attacker’s pace is not about a faster dashboard. It needs a different division of work between machines and people.
Every alert read, immediately
Nothing waits in a queue for its turn. Each alert is read as it arrives and placed with the host, account or service it concerns.
Context assembled automatically
What is normal for this entity, what else it did recently and what the logs show are gathered before a person is involved.
Stories, not fragments
Related signals are kept together as one case with one timeline, so the intrusion is seen as an intrusion.
Conclusions checked against evidence
Speed without verification produces fast mistakes. Each conclusion should be traceable to raw evidence a person can inspect.
Response ready to approve
When action is warranted, the proposal, its evidence and its rollback are already prepared, so the human decision takes minutes, not hours.
Learning from outcomes
Each settled case should make the next one faster, so speed improves with time rather than depending on who is on shift.
Keeping people in charge
Machine speed does not mean removing people. It means moving them to where their judgement matters: approving actions, handling the genuinely ambiguous cases and setting policy. The routine parts of triage and investigation, which consume most of an analyst’s day, are the parts machines can now do faster and more consistently.
Trust has to be earned in steps. A sensible path is to let an autonomous system work alongside analysts first, compare its conclusions with theirs, and widen its autonomy one capability at a time as the evidence supports it. Response stays proposal-first, with a person approving each action and an audit trail of every step.
This is the approach behind ApexAI: an autonomous SOC that reads every alert, builds the story and proposes the response at machine speed, while people keep the decision. You can read more about the wider problem on our Why ApexAI page.
Questions
What is breakout time?
Breakout time is the time between an attacker gaining initial access to one system and moving laterally to another. A short breakout time leaves defenders very little room to contain an intrusion.
Why can’t more analysts solve the speed problem?
More analysts shorten the queue but do not remove the steps of opening, enriching, correlating and escalating each alert. Those steps take longer than a modern breakout, so the pace of the work has to change, not just its capacity.
Does machine-speed defence mean automated containment without approval?
No. Detection, investigation and the preparation of a response can run at machine speed while a person still approves each action. Prepared proposals make that approval fast.
Sources
Third-party figures, as published by their sources.
- CrowdStrike, 2026 Global Threat Report (press release, February 2026)
- Mandiant / Google Cloud, How Low Can You Go? An Analysis of 2023 Time-to-Exploit Trends (October 2024)
- Verizon, 2025 Data Breach Investigations Report (news release, 2025)
- Mandiant / Google Cloud, M-Trends 2025
- IBM, Cost of a Data Breach Report 2025 (press release, July 2025)
See ApexAI on your own alerts.
A walkthrough with your team, in observe mode first: ApexAI scores and proposes, nothing acts on its own.