Nullify

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Product Security Terms›
Mean Time to Remediate

Product Security Terms

Mean Time to Remediate

NT
Tim Thacker
November 14, 2026

What Is
Mean Time to Remediate
?

Mean time to remediate (MTTR) is the average time it takes to fix a security vulnerability, measured from when it is detected or disclosed to when the fix is deployed or the finding is closed. It is the most common measure of how quickly a security program turns findings into fixes.

Also known as:

mean time to remediation, mean time to resolve, time to fix

How MTTR Is Calculated

MTTR is the total time to remediate a set of vulnerabilities divided by the number of vulnerabilities fixed. If three critical findings took 4, 10 and 16 days to fix, the MTTR for that group is 10 days. The result depends on two choices that teams should write down: when the clock starts (detection, disclosure, triage or ticket creation) and when it stops (fix merged, fix deployed or finding verified closed).

Why Teams Track MTTR by Severity

A single MTTR across every finding hides the numbers that matter. Teams usually report it separately for critical, high, medium and low findings, and for actively exploited vulnerabilities. A fast overall average can still mean criticals wait weeks while easy low-severity fixes pull the number down.

What Slows MTTR Down

  • Triage queues. Findings wait until someone confirms they are real and reachable.
  • Unclear ownership. No one is sure which team should fix the issue.
  • Fix effort. Writing, testing and reviewing the change takes engineering time away from feature work.
  • Broken builds. An upgrade fails CI and the fix stalls until someone repairs it.
  • No escalation. Stalled work goes unnoticed until the SLA has already slipped.

MTTR and Remediation SLAs

MTTR describes what happened on average, while a remediation SLA sets the deadline each finding must meet. The two work together: SLA compliance shows how many findings were fixed on time, and MTTR shows how much time the program needs overall. Improving MTTR without filtering false positives first can be misleading, because closing noise quickly lowers the average without reducing risk.

How Nullify Cuts MTTR

Nullify takes the waiting out of each step. It filters unreachable and false-positive findings before review, routes each fix to the owner from commit history and CODEOWNERS, writes a minimal fix validated against the build before the pull request opens and repairs CI failures until it passes. Stalled work is escalated in Slack against your SLA, and developers approve every merge. Across customers, mean time to resolve fell from 11.8 days to 5.4 days. See how Nullify fixes and routes findings.

Key Takeaways

  • MTTR is the average time from detecting a vulnerability to fixing it.
  • Define when the clock starts and stops, and report MTTR by severity.
  • Triage queues, unclear ownership, fix effort and broken builds slow it down.
  • Pair MTTR with SLA compliance, and filter false positives so the number reflects real risk.

Read More About
Mean Time to Remediate

Reduce MTTR

See Nullify in Action

Nullify proves what is real, writes the fix and chases it to merge, so criticals land inside SLA.

See how to reduce MTTR

Reduce your vulnerability backlog and lower your MTTR

The AI harness that finds, proves and fixes vulnerabilities across your codebase.

Book a demo