Dwell Time
Qu'est-ce que 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.
● Exemples
- 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.
● Questions fréquentes
Qu'est-ce que 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. Cette notion relève de la catégorie Défense et opérations en cybersécurité.
Que signifie 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.
Comment fonctionne Dwell Time ?
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.
Comment se défendre contre Dwell Time ?
Les défenses contre Dwell Time combinent habituellement des contrôles techniques et des pratiques opérationnelles, comme détaillé dans la définition ci-dessus.
Quels sont les autres noms de Dwell Time ?
Noms alternatifs courants : Attacker dwell time, Compromise-to-detect time.
● Termes liés
- defense-ops№ 735
MTTD (temps moyen de détection)
Temps moyen écoulé entre le début d'un incident de sécurité et le moment où les défenseurs l'identifient.
- defense-ops№ 734
MTTC (temps moyen de confinement)
Temps moyen entre la détection d'un incident et le moment où la menace ne peut plus se propager, exfiltrer des données ou aggraver l'impact.
- defense-ops№ 737
MTTR (temps moyen de réponse)
Temps moyen entre la détection d'un incident de sécurité et le démarrage d'une action de réponse efficace.
- defense-ops№ 736
MTTR (temps moyen de rétablissement)
Temps moyen nécessaire pour ramener les systèmes et services affectés à un fonctionnement normal après un incident de sécurité ou une indisponibilité.
- forensics-ir№ 582
Réponse à incident
Processus organisé permettant de préparer, détecter, analyser, contenir, éradiquer puis récupérer suite à un incident de cybersécurité, en capitalisant sur les leçons apprises.
- defense-ops№ 1267
Threat Hunting
Recherche proactive et fondée sur des hypothèses dans la télémétrie pour identifier des menaces ayant échappé aux détections existantes.