Dwell Time
What is Dwell Time?
Dwell TimeThe interval between an adversary's initial compromise of an environment and the defender's detection of that compromise — a headline industry metric reported annually by IR firms such as Mandiant.
Dwell time is the duration between initial intrusion and detection (sometimes broken into 'attacker dwell' until any defender action and 'detection dwell' until first confirmed alert). It is the single most cited efficacy metric in industry incident-response reports — Mandiant's M-Trends, IBM/Ponemon, CrowdStrike — and tracks how successful defenders are at finding adversaries before they finish their objectives. Historically median dwell times were measured in many months (Mandiant reported 416 days in 2011); by 2023–2024 medians had fallen to around 10 days globally for externally-notified incidents and a few days for ransomware-driven cases, both because attackers moved faster (ransomware shifted to days-to-encryption) and because defenders deployed better tooling (EDR, SIEM rule coverage, MDR). Dwell time alone can be misleading — fast detection of a brief intrusion may be worse than slow detection of a long one — so mature programs report it alongside Mean Time to Contain and Mean Time to Recover.
● Examples
- 01
A red-team retrospective records a 21-day dwell from initial AWS key compromise to first alert; the after-action focuses on cloud-control-plane detections.
- 02
A board update reports that median dwell time fell from 32 days last year to 7 days this year following EDR + MDR rollout.
● Frequently asked questions
What is Dwell Time?
The interval between an adversary's initial compromise of an environment and the defender's detection of that compromise — a headline industry metric reported annually by IR firms such as Mandiant. It belongs to the Defense & Operations category of cybersecurity.
What does Dwell Time mean?
The interval between an adversary's initial compromise of an environment and the defender's detection of that compromise — a headline industry metric reported annually by IR firms such as Mandiant.
How does Dwell Time work?
Dwell time is the duration between initial intrusion and detection (sometimes broken into 'attacker dwell' until any defender action and 'detection dwell' until first confirmed alert). It is the single most cited efficacy metric in industry incident-response reports — Mandiant's M-Trends, IBM/Ponemon, CrowdStrike — and tracks how successful defenders are at finding adversaries before they finish their objectives. Historically median dwell times were measured in many months (Mandiant reported 416 days in 2011); by 2023–2024 medians had fallen to around 10 days globally for externally-notified incidents and a few days for ransomware-driven cases, both because attackers moved faster (ransomware shifted to days-to-encryption) and because defenders deployed better tooling (EDR, SIEM rule coverage, MDR). Dwell time alone can be misleading — fast detection of a brief intrusion may be worse than slow detection of a long one — so mature programs report it alongside Mean Time to Contain and Mean Time to Recover.
How do you defend against Dwell Time?
Defences for Dwell Time typically combine technical controls and operational practices, as detailed in the full definition above.
What are other names for Dwell Time?
Common alternative names include: Attacker dwell time, Compromise-to-detect time.
● Related terms
- defense-ops№ 735
Mean Time to Detect (MTTD)
The average elapsed time between the start of a security incident and the moment defenders identify it.
- defense-ops№ 734
Mean Time to Contain (MTTC)
The average time between detecting a security incident and reaching a state where the threat can no longer spread, exfiltrate, or cause further damage.
- defense-ops№ 737
Mean Time to Respond (MTTR)
The average time between detecting a security incident and initiating an effective response action against it.
- defense-ops№ 736
Mean Time to Recover (MTTR)
The average time required to restore affected systems and services to normal operation after a security incident or outage.
- forensics-ir№ 582
Incident Response
The organised process of preparing for, detecting, analysing, containing, eradicating, and recovering from cyber security incidents, then capturing lessons learned.
- defense-ops№ 1267
Threat Hunting
Proactive, hypothesis-driven search through telemetry to uncover threats that have evaded existing detections.