Support period under the Cyber Resilience Act: at least five years?
3 min read
During the support period, the manufacturer must handle vulnerabilities in its product and provide security updates. The Cyber Resilience Act sets five years as the minimum – with one exception. This guide summarises what Article 13 lays down.
What it is about
When placing a product on the market, and for the support period, the manufacturer ensures that vulnerabilities of the product, including its components, are handled effectively and in accordance with Annex I, Part II (Art. 13(8)). This includes addressing vulnerabilities without delay and providing security updates – where technically feasible, separately from functionality updates.
These obligations apply from 11 December 2027 (Art. 71(2)).
Source: Art. 13(8) CRA · Annex I, Part II, point 2 CRA · Art. 71(2) CRA
How long the period must be
The manufacturer determines the support period so that it reflects the length of time the product is expected to be in use. It must take into account, in particular, reasonable user expectations, the nature of the product including its intended purpose, and relevant Union law on the lifetime of products.
It may also take into account the support periods of comparable products from other manufacturers, the availability of the operating environment, the support periods of integrated components that provide core functions and are sourced from third parties, and guidance from the ADCO group and the Commission.
The period is at least five years. It may only be shorter if the product is expected to be in use for less than five years – it then corresponds to the expected time of use.
The considerations that led to the chosen period belong in the technical documentation. The Commission may set minimum periods for specific product categories by delegated act where market surveillance data indicate inadequate periods.
Source: Art. 13(8) CRA
State the end date
- The end date must be specified clearly and be easily accessible at the time of purchase – at least month and year, where applicable on the product, its packaging or by digital means (Art. 13(19)).
- The information for users states the type of technical security support and the end date (Annex II, point 7).
- Where technically feasible, the manufacturer displays a notification to users when the support period has ended (Art. 13(19)).
Source: Art. 13(19) CRA · Annex II, point 7 CRA
Security updates: free of charge and available for a long time
- Security updates are disseminated without delay and free of charge, accompanied by advisory messages on possible action. Exception: for a tailor-made product, the manufacturer and a business user may agree otherwise (Annex I, Part II, point 8).
- Each security update made available during the support period remains available for at least ten years or for the remainder of the support period, whichever is longer (Art. 13(9)).
Source: Annex I, Part II, point 8 CRA · Art. 13(9) CRA
Several software versions
Where a manufacturer has placed on the market subsequent substantially modified versions of a software product, it may limit the handling of vulnerabilities to the version it placed on the market last – provided that users of earlier versions have access to the latest version free of charge and do not incur additional costs to adjust their hardware and software environment (Art. 13(10)).
Source: Art. 13(10) CRA
Retention
The manufacturer keeps the technical documentation and the EU declaration of conformity for at least ten years after placing on the market or for the support period, whichever is longer (Art. 13(13)). The same duration applies to the information for users under Annex II (Art. 13(18)).
Source: Art. 13(13), (18) CRA
In practice
- Record the reasons for the period for each product: expected time of use, customer expectations, support periods of the integrated third-party components.
- State the end date on the website, packaging or product page, at least month and year.
- Compare the support periods of the integrated components with your own period – if support for a core component ends earlier, you need a plan.
- Think of the notification to users in good time before the end.
Related guides
- Product and evidenceWhat is an SBOM? Obligations under the Cyber Resilience Act3 min read
- Product and evidenceTechnical documentation under the Cyber Resilience Act7 min read
- Product and evidenceEU declaration of conformity under the Cyber Resilience Act4 min read
- Product and evidenceUser information under Annex II CRA: what must accompany a product8 min read
Terms in the Cyber Resilience Act glossary
Sources
First published 19 Oct 2026, last updated 19 Oct 2026. This guide reflects the wording of the regulation and the Commission’s guidelines and does not constitute legal advice.