Mean Time to Respond (MTTR)

Mean time to respond (MTTR) is the average time between detecting a security incident and containing or resolving it. Together with mean time to detect, it shows how quickly a security team limits the damage from an attack.

IntermediateCategory: Monitoring, testing and incident response

Also called: MTTR, mean time to contain, MTTC, mean time to recover, mean time to remediate

What is mean time to respond?

Detecting an attack is only half the job. Mean time to respond (MTTR) measures how long it takes, on average, to act once an incident is detected: to contain it so the attacker can't do more damage, and ideally to resolve it.

The acronym is used loosely, so it's worth asking which version someone means:

  • Mean time to respond: detection to first meaningful action, such as isolating a device
  • Mean time to contain (MTTC): detection to the threat being stopped from spreading
  • Mean time to recover: detection to normal operations restored
  • Mean time to remediate: detection to the root cause, such as a vulnerability, being fixed

In IBM's 2025 Cost of a Data Breach study, organizations took an average of 60 days to contain a breach after identifying it.

Why it matters

Every hour an attacker keeps access is another hour to steal data or spread ransomware. Ransomware groups often move from first access to encryption quickly, so a response that waits until Monday morning can be too late. IBM's research finds that breaches contained faster tend to cost less.

How it's measured

MTTR = total response time for all incidents ÷ number of incidents

Track it separately for different severities. A fast average can hide a slow response to the incidents that matter most.

How to reduce MTTR

  1. Have an [incident response plan](/glossary/incident-response-plan/) and [playbooks](/glossary/incident-response-playbook/) so nobody wastes time deciding what to do.
  2. Pre-authorize containment. Let your IT or security provider isolate a device or disable an account without waiting for approval.
  3. Use tools that can act, such as EDR that isolates machines with one click, and automation through SOAR.
  4. Keep an [incident response retainer](/services/incident-response/) so experts start in hours, not days.
  5. Practice with tabletop exercises.
  6. Keep tested backups to shorten recovery.

Managed detection and response providers often include containment in their service. Ask whether they'll act on your behalf or just notify you.

Related terms

Sources

  1. Cost of a Data Breach Report 2025 (IBM)
  2. What Is SOAR? (Microsoft)

Drafted with AI assistance, then edited and fact-checked by a person. How we use AI.