← CRA Glossary
Incident Response & Operations

Mean Time to Remediate (MTTR)

Mean Time to Remediate (MTTR) is a security operations metric that measures the average time elapsed between a vulnerability being identified (or reported) and a fix being deployed to affected systems. For CRA manufacturers, MTTR is a key performance indicator for demonstrating that vulnerabilities are addressed 'without undue delay' as required by Annex I.

Mean Time to Remediate (MTTR) is a security operations metric that measures the average time elapsed between a vulnerability being identified (or reported) and a fix being deployed to affected systems. For CRA manufacturers, MTTR is a key performance indicator for demonstrating that vulnerabilities are addressed 'without undue delay' as required by Annex I.

Incident Response & Operations

Last updated 19 July 2026

What Is Mean Time to Remediate (MTTR)?

Mean Time to Remediate (MTTR) is a metric that quantifies the average time between a security vulnerability being identified and a fix being deployed to all affected systems or users. MTTR can be measured at multiple points: from vulnerability identification to patch available (development MTTR); from patch available to patch deployed in production (deployment MTTR); or end-to-end from identification to full fleet remediation. In the context of CRA manufacturer obligations, MTTR primarily refers to the time from vulnerability identification (through CVD report, CVE disclosure, or internal discovery) to security update being available to users. Deployment MTTR is largely outside the manufacturer's control - it depends on users' patching practices - but publishing security updates promptly is the manufacturer's obligation.

CRA reference:Annex I, Article 13

MTTR as a CRA Compliance Metric

The CRA requires manufacturers to address vulnerabilities 'without undue delay'. MTTR is the primary quantitative measure of how well a manufacturer meets this obligation. Industry benchmarks and ENISA guidance provide reference points:

  • Critical (CVSS 9.0–10.0): Target MTTR of 30 days or fewer for patch availability. Interim mitigation guidance within 5 days.
  • High (CVSS 7.0–8.9): Target MTTR of 60 days for patch availability.
  • Medium (CVSS 4.0–6.9): Target MTTR of 90 days, includable in planned release cycles.
  • Actively exploited (any severity): Emergency response - patch or mitigation guidance within days; ENISA notification within 24 hours of confirmed exploitation.

Manufacturers should track MTTR by severity band and review it regularly. A consistent trend of exceeding SLA targets is an early warning of a compliance risk and a process capacity issue.

CRA reference:Annex I, Article 13

Factors That Drive MTTR Performance

MTTR is influenced by multiple factors across the vulnerability handling workflow:

  • Triage speed: Slow triage (days to validate and score a vulnerability) delays the start of remediation. Automated SBOM-based CVE correlation reduces triage time for known CVEs.
  • Development process: A development team that can context-switch to security patches quickly has lower MTTR. Teams with rigid sprint structures and no emergency patch capacity have higher MTTR for critical vulnerabilities.
  • Testing requirements: Safety-critical products with extensive regression testing requirements have structurally higher MTTR due to test cycle length. This should be reflected in the PSIRT SLA - a longer target MTTR for these products is legitimate if justified by testing constraints.
  • Build and release automation: Manual build and release processes add days to MTTR. CI/CD automation that enables rapid emergency releases significantly reduces MTTR.
  • OTA update infrastructure: Products with OTA capability have lower effective MTTR (from user's perspective) than products requiring manual update procedures.
CRA reference:Annex I, Article 13

Measuring and Improving MTTR

To measure and improve MTTR, manufacturers need:

  • Tracking system: A vulnerability case management system (PSIRT ticketing) that records the date of identification, date of fix availability, and date of advisory publication for each vulnerability.
  • Reporting: Regular MTTR reports by severity band, ideally reviewed in monthly PSIRT performance reviews and reported to senior management quarterly.
  • Root cause analysis: For SLA misses, conduct root cause analysis - was the miss due to triage delays, development capacity constraints, testing cycle length, or release process bottlenecks? Different root causes require different remediation investments.
  • Trend tracking: Track MTTR trends over time. An increasing MTTR trend despite constant vulnerability volume suggests process degradation. A decreasing trend demonstrates continuous improvement.

CVD Portal tracks MTTR automatically from intake to advisory publication, providing the reporting data needed for CRA compliance evidence.

Work through the CRA for each product in one workspace.

Classify each product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.

Frequently asked

Is MTTR the same as time-to-patch?+

MTTR and time-to-patch are related but have different measurement endpoints. Time-to-patch typically measures the time for a patch to be developed and made available. MTTR can additionally measure the time for the patch to be fully deployed across all affected systems. For CRA purposes, the manufacturer's primary obligation is to make the patch available - deployment MTTR is influenced by user behaviour outside the manufacturer's control. Manufacturers should track both, noting that their CRA obligation is met when the patch is published and users are notified.

How does MTTR relate to the CRA's 'without undue delay' standard?+

The CRA's 'without undue delay' standard is operationalised by MTTR targets. A manufacturer with documented MTTR targets (e.g., Critical: 30 days, High: 60 days) and a track record of meeting them has strong evidence that it addresses vulnerabilities without undue delay. A manufacturer with no MTTR tracking and high-severity vulnerabilities left open for months has no documentary basis for claiming compliance with this standard. Documented MTTR reporting is therefore a key piece of CRA compliance evidence.

What is a reasonable MTTR for products in safety-critical industries?+

Safety-critical products - medical devices, industrial controllers, automotive systems - have structurally higher MTTR due to extensive regulatory testing requirements before any software update can be released. For these products, a Critical MTTR of 90 days rather than 30 days may be appropriate, provided: interim mitigation guidance is issued promptly; the manufacturer maintains documented records of the testing requirements justifying the longer timeline; and regulators (MSAs, Notified Bodies) are aware of and agree to the sector-specific constraints. ENISA acknowledges sector-specific constraints in its guidance.

Sector checklists covering Mean Time to Remediate (MTTR)

Consumer Routers & ModemsConsumer routers and modems are high-value targets for attackers and face specific CRA requirements around default credentials, remote management security, and firmware update integrity. Routers, internet modems, switches and wireless access points are Important Class I (Annex III, point 12), for home, industrial and critical infrastructure markets alike. No CRA harmonised standard is cited yet, so today a router needs a notified body for conformity assessment (Article 32(2)).Smart Home DevicesSmart home devices, such as thermostats, smart speakers, lighting controllers and home security cameras, are among the most common products with digital elements in scope for the CRA. Thermostats and lighting controllers are default class, and Module A internal control is open to them (Article 32(1)). A smart speaker with a general purpose virtual assistant is Important Class I (Annex III, point 16). A home security camera, smart lock, baby monitor or alarm system is Important Class I (Annex III, point 17). So is a hub or software that centrally controls these security products.Enterprise Networking EquipmentEnterprise networking equipment - switches, firewalls, load balancers, and network management systems - spans multiple Annex III classifications. Firewalls in hardware or software form and intrusion detection and prevention systems are Important Class II. Switches, routers, wireless access points, network management systems and SIEM systems are Important Class I. A load balancer is default class unless its core functionality is a listed category, such as a web application firewall. Class II products always need third-party conformity assessment (Article 32(3)). Class I products need a notified body today, because no CRA harmonised standard is cited yet (Article 32(2)).Medical DevicesMedical devices regulated under the EU Medical Device Regulation (MDR) or In Vitro Diagnostic Regulation (IVDR) are generally excluded from the CRA. However, software products used in healthcare that are not classified as medical devices under MDR may fall within CRA scope. Manufacturers should carefully verify their product's regulatory classification.

This definition is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.

Browse the full CRA Compliance Checklist

See how Mean Time to Remediate (MTTR) fits into your complete CRA compliance programme.

View checklists →