Mean Time to Respond
Also called MTTR.
Average time from detecting an incident to responding to it.
What it is
Mean Time to Respond is the average elapsed time between detecting an incident and taking effective response action, such as containment. It measures how quickly a team acts once it knows something is wrong.
Why it matters
Detection alone is not enough. Slow response still lets damage accumulate, so MTTR captures the operational speed of containment and is often a driver behind automation and clear escalation paths.
In practice
Reducing MTTR by automating host isolation so containment happens in minutes instead of waiting for manual action.
What to look for
- Time from alert to containment.
- Delays waiting on approvals or access.
- Automations that shortened response.
Common mistake
Averaging everything together. A few large incidents can hide slow response on common ones.
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 SOAR Commercial
Runs playbooks that enrich alerts and take response actions across tools.
-
Cortex XSOAR Commercial
Palo Alto Networks' SOAR platform with case management and playbooks.
-
Tines Commercial
Builds automated workflows that connect security tools without heavy code.
Read next
- Mean Time to Detect: Average time from an intrusion starting to its detection.
- Containment: Stopping an incident from spreading while you investigate.
- SOAR: Automating and orchestrating response steps across security tools.