Three Ways Breaches Get Found: The 204-Day Number That Should Worry You
Archi4 min read
Contents
The number that outlasts every tool you buy#
Most security budgets assume a breach is caught by the team that owns the network. The data says otherwise. When researchers and incident responders publish detection timelines, the pattern repeats across industries and company sizes: an intruder who gains a foothold is likely to keep it for months, and the first alarm frequently comes from someone outside the building.
A widely cited industry figure for median time to identify a breach has hovered between roughly 200 and 210 days for years. This article compares the three channels through which breaches actually get found, and asks why the internal detection channel, the one everyone funds, is the slowest of the three.
Channel one: an outsider tells you#
This is the most common and least flattering path. A customer notices unusual account activity. A fraud analyst at a payment processor flags a pattern. A researcher finds a misconfigured storage bucket and emails the address in the WHOIS record. A law enforcement contact or a national CERT reaches out after intelligence surfaces on a criminal forum.
The surprise is not that outsiders find breaches. It is how often they arrive before the internal team has a ticket open. That gap is the entire point of the 204-day figure. It measures the distance between compromise and awareness, and a large share of that distance is spent with nobody looking in the right place.
External reports also tend to arrive with a clock attached. Once a partner or regulator knows, disclosure deadlines start moving. The response team inherits a public-facing problem before it has finished scoping the technical one.
Channel two: someone reads the logs#
Internal detection through monitoring, endpoint telemetry, and alerting is the channel most mature teams build first. It works, and it works fast when the alert rules match the actual attack. A password spray against a VPN endpoint trips a threshold within minutes. A newly created admin account triggers a review.
The weakness is coverage, not speed. Detection depends on the log existing, shipping to a place where it can be queried, and having a rule that fires on the specific behavior. Attackers who live off legitimate tools, use valid credentials, and move slowly can stay inside the noise floor for a long time. Every added data source raises cost, and every quiet quarter tempts someone to cut retention.
The comparison here is stark: internal detection is the fastest channel when it works and the slowest when it misses, because nothing else prompts a look.
Channel three: the attacker slips or sells#
A smaller share of discoveries comes from the intrusion itself failing. Infrastructure gets abandoned after a payment dispute. A ransomware affiliate leaks negotiation chats. A broker advertises access on a forum and a threat intelligence vendor spots it.
This channel is real but unreliable. It rewards organizations that monitor criminal marketplaces and track their own leaked credentials. It punishes anyone who treats threat intelligence as a newsletter subscription rather than a feed wired into alerting.
Comparing the three on what matters#
| Channel | Typical speed | Signal quality | Cost to build |
|---|---|---|---|
| Outside party | Slow, often after data leaves | High, hard to dismiss | Low, but reputationally expensive |
| Internal telemetry | Minutes to days when tuned | Mixed, prone to noise | High |
| Attacker error or market chatter | Unpredictable | Variable | Moderate |
Read the table as a budget argument. The channel with the best signal quality is the one you do not control. The channel you control is the one most likely to miss. That inversion explains why the median detection figure has resisted a decade of product spending.
What actually moves the median#
Three practices show up repeatedly in incident reviews where detection came early rather than late.
First, identity logging with retention measured in months, not weeks. Most modern intrusions use stolen credentials, so authentication events matter more than perimeter alerts.
Second, a tested path for outside reports. A working security contact, a monitored inbox, and a documented triage step turn a stranger's email into an investigation instead of a scramble.
Third, rehearsed scoping. Teams that can answer "which accounts touched this host in the last 30 days" within an hour collapse the expensive part of the timeline. Teams that cannot spend the first week building the query.
None of these require a new platform. They require deciding that the detection gap is a process problem wearing a technology costume.
The uncomfortable comparison#
If you stack the three channels against spending, the mismatch is obvious. Internal detection gets the tools and the headcount. External reporting gets almost nothing, yet it produces a large share of discoveries. Attacker-side intelligence gets a fraction of the budget and occasionally delivers the earliest warning of all.
A reasonable rebalance is not dramatic. Fund the boring parts: retention, identity telemetry, an outside report intake that a stranger can find and use. The 204-day number will not fall because of a new sensor. It will fall when the slowest channel stops being the default.
More articles