All Glossaries
1
min read
Table of Contents

MTTx: MTTD, MTTA, MTTR and MTTC

What is MTTx?

MTTx is shorthand for the family of "mean time to" metrics that security teams use to measure speed, where the x stands for the stage being measured: detect, acknowledge, respond, contain and so on. Together they show where time goes between an attack starting and an attack being stopped.

The main MTTx metrics

Metric

Measures time from

To

MTTD: mean time to detect

Start of malicious activity

First alert or detection

MTTA: mean time to acknowledge

Alert

First action by an analyst or agent

MTTI: mean time to investigate

Acknowledgment

Verdict on what happened

MTTC: mean time to contain

Alert or detection

Threat contained, such as host isolated

MTTR: mean time to respond or remediate

Alert or detection

Response complete or systems restored

‍

A related measure, dwell time, is the total time an attacker is present before being detected or removed.

How do you calculate MTTx?

Each MTTx metric is the sum of the durations for a set of incidents divided by the number of incidents. For MTTD:

MTTD = total (detection time − compromise start time) ÷ number of incidents

The hard part is not the arithmetic but the timestamps. The start of malicious activity is often only known after investigation, and teams define "contained" and "resolved" differently. Write your definitions down and apply them the same way every time.

Why does MTTR mean different things?

MTTR means different things because the R can stand for respond, remediate, resolve or recover, depending on the team and the tool. Mean time to respond might stop when containment starts, while mean time to recover might stop when systems are fully restored days later. When comparing numbers across teams, vendors or reports, check which R is meant. Using separate MTTC and recovery metrics avoids the confusion.

Common MTTx pitfalls

  • Averages hide outliers. Report medians and the slowest cases too.
  • Mixing incident types. Phishing and ransomware have very different timelines. Segment by type.
  • Gaming the clock. Closing tickets early improves the number but not security. Pair speed metrics with accuracy metrics, as described in measuring an agentic SOC.
  • Ignoring what was missed. MTTD only covers detected incidents. Attacks you never caught do not appear at all.

Frequently asked questions

Which MTTx metric matters most?

It depends on your goals, but MTTD and MTTC are usually the most telling: how quickly you notice an attack and how quickly you stop it from spreading.

How do AI agents affect MTTx?

Agents usually reduce MTTA and MTTC the most, because they remove time alerts spend waiting in a queue and can contain clear threats immediately within approved limits.

Should we use mean or median?

Track both. The mean reflects the cost of long incidents, while the median shows typical performance.

Anomali and MTTx

Anomali helps reduce MTTD and MTTC by enriching data at ingest and using AI agents for triage and investigation, so alerts spend less time waiting for context or a person.

Request a demo to see how Anomali shortens response times.

Read next

‍