Home / Glossary / Mean time to remediate (MTTR)
Glossary, read 12 Nov 2026
Mean time to remediate (MTTR), defined for a CTEM program
Mean time to remediate (MTTR) in practice
MTTR is useful only when segmented. A single program-wide average hides the items that matter: KEV-listed flaws on internet-facing crown-jewel assets can age for months inside an average pulled down by thousands of quick automated patches. Report MTTR by priority tier, by asset class and by owning team, and show the median next to the mean so a few very old items stand out.
Two definitions need settling before the number means anything. First, when the clock starts: first detection, first ticket, or KEV listing date. Second, when it stops: patch deployed, scanner confirms, or validation proves the path is closed. CTEM programs that stop the clock only after re-validation report longer but more honest MTTR.
An example
Rapid7's Exposure Management dashboard documentation (read 12 Nov 2026) includes MTTR trend views by vulnerability severity and for cloud versus on-premises assets.
Source, read 12 Nov 2026.
Related terms
Sources
- https://docs.rapid7.com/exposure-command/executive-risk-view/, read 12 Nov 2026
- https://www.brinqa.com/platform/remediate-at-scale, read 12 Nov 2026
Last reviewed 12 Nov 2026.