Mean Time to Detect
Also called MTTD.
Average time from an intrusion starting to its detection.
What it is
Mean Time to Detect is the average elapsed time between when a threat or incident begins and when it is detected. It is a core program metric measuring how quickly defenders notice activity.
Why it matters
Lower MTTD means adversaries have less time to act before defenders respond. That makes it a headline measure of detection effectiveness, and a primary target for hunting and detection-engineering investment.
In practice
Tracking MTTD across incidents and finding it dropped from weeks to days after a new detection program took hold.
What to look for
- Gap between first attacker activity and first alert.
- Incidents found by outside parties.
- Long dwell times in specific environments.
Common mistake
Measuring from the first alert. Detection time starts when the attack started.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Splunk Enterprise Security Commercial
A SIEM where these logs are searched with SPL and turned into correlation searches.
-
Microsoft Sentinel Commercial
Microsoft's cloud SIEM, queried with KQL and fed by connectors for these log sources.
-
Elastic Security Commercial
A SIEM built on Elasticsearch, with a detection rules library and timeline investigations.
-
Wazuh Open source
An open source platform that collects, decodes and alerts on host and log data.
Read next
- Mean Time to Respond: Average time from detecting an incident to responding to it.
- Detection Coverage: How much of relevant adversary behavior your detections actually catch.
- Triage: Quickly assessing alerts to decide what's real and what's urgent.