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.
A related measure, dwell time, is the total time an attacker is present before being detected or removed.
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.
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.
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 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.