Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Mean time to respond measures what happens after detection. The abbreviation MTTR is used for four different intervals, which is why the first task is deciding which one you are reporting.

What Is Mean Time to Respond?
Mean time to respond measures the interval between detecting malicious activity and doing something effective about it. It is the natural companion to mean time to detect, and it is reported far more loosely, because the same abbreviation is routinely used for respond, remediate, recover, and resolve, which are four different things with four different owners.
| Measure | Ends when | Typical owner |
|---|---|---|
| Time to acknowledge | A human picks the case up | SOC |
| Time to contain | Spread and further damage stop | SOC and infrastructure |
| Time to eradicate | Attacker access is removed | Incident response |
| Time to recover | Service is restored to normal | IT and business owners |
Reporting a single blended figure hides where the delay actually occurs, and the delay is rarely where people assume. Teams that break the interval into stages usually find that acknowledgement and containment are fast, and that the hours disappear in obtaining authority to act, or in waiting for a system owner to approve an outage.
Of the four, time to contain has the clearest relationship to loss. Ransomware deployment from first access to encryption has compressed steadily, and in some observed intrusions it now runs in hours rather than days. An organisation that contains in two hours and an organisation that contains in two days experience entirely different incidents from the same intrusion.
Measure it from detection to the point where the attacker can no longer progress: the host isolated, the account disabled, the credential revoked, the egress blocked. Partial containment, such as isolating one host while the attacker holds credentials for five others, should not stop the clock, and recording it honestly is what turns the metric into a diagnostic rather than a score.
Faster is not always better. Containing immediately destroys the opportunity to understand scope, and an attacker who notices one isolated host may accelerate to destructive action on the others. Isolating a machine without capturing memory first can lose the only evidence of what ran. And a rushed containment that misses one of the attacker’s three footholds produces a second incident a week later, which the metric records as a new case rather than as a failure of the first.
The mature position is to measure response time while judging response quality separately: was scope established before containment, was evidence preserved, did the attacker return. A team that drives the headline number down while re-opening a third of its incidents is going backwards.
Segment by severity, because mixing a routine malware case with a domain-wide compromise produces an average that describes neither. Report median and mean together, state the sample size, and show the stage breakdown rather than the total alone. Add the proportion of incidents that recurred within 30 days, which is the quality counterweight.
For UK organisations there is also an external clock to acknowledge. Notification to the Information Commissioner’s Office is due within 72 hours of becoming aware of a personal data breach, and NIS Regulations and FCA obligations run in parallel. Those deadlines are not measures of technical response, but they belong on the same timeline, because the decisions they require compete for the same people. Our investigation and incident response services are structured around that competition rather than ignoring it.
It is used for mean time to respond, remediate, recover, and resolve, and the four measure different intervals ending at different points. Before reporting the figure, define which one you mean and where the clock stops. Most security teams should measure time to contain, because that interval has the clearest relationship to the damage an incident causes.
For a high-severity case involving active attacker presence, within an hour of detection is a sound target, and achieving it depends far more on pre-agreed authority than on tooling. Lower severities can reasonably run to hours. Set targets per severity, measure against them, and investigate the cases that miss, because the cause is usually a specific approval step rather than general slowness.
For reversible, low-impact actions on standard endpoints, yes: session revocation, credential resets, and isolation of user workstations are good candidates. For servers, domain controllers, and operational technology, keep a human in the decision, because an incorrect automated containment causes exactly the outage the attacker wanted. Guardrails such as asset exclusions, rate limits, and automatic expiry are essential either way.
Yes. Immediate containment can destroy volatile evidence, alert the attacker and prompt destructive action, and miss additional footholds that only a scoping exercise would have found. Capture memory before isolating where the capability exists, establish the full extent of access before acting where the risk allows it, and track incidents that recur within 30 days as a check on rushed response.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.