Guide
Support periods and security updates
Manufacturers must support each product for at least five years, or its expected use time if that is shorter, and say how long. Updates must stay available beyond that.
Last reviewed against European Commission, National Cyber Security Centre Ireland and cyberresilienceact.eu. Sources
The rule
Five years as a floor
Article 13 sets a support period of at least five years, or the expected use time if shorter [4]. Security updates must remain available for at least 10 years after issue, or for the remainder of the support period if that is longer [4]. The Commission guidance calls the five years a minimum safeguard only, and says support should reflect realistic use time [7].
Versions
One period per release
Decisions
What to settle
The declared period
Choose a period per product that matches how long customers will use it. A short period on a long-lived device will be hard to defend.
Update delivery
Decide how fixes reach users and whether they install automatically. Free upgrades are the condition for limiting support to the newest version [7].
Records
Technical documentation and the declaration of conformity must be kept for 10 years or the support period, whichever is longer [4].
Interaction
Modification and reassessment
A substantial modification triggers a reassessment of the support period, but does not automatically reset or extend it [7]. Skadden adds that from December 2027 security risks must be addressed through updates during the support period [5].
Read the gap assessment guide to see where your update process falls short, or the fines page for the consequences.
Treat it as a cost line
A support period is a commitment to staff, tooling and release processes for years. Put it in the product business case at design stage.
Keep reading
Read next
UK manufacturers
How the EU Cyber Resilience Act reaches UK manufacturers without an EU office: authorised representatives, importers, where reports go and open questions.
Read the guide
UK comparison
How the EU Cyber Resilience Act and the UK PSTI product security regime differ in scope, duties and enforcement, and what the UK bill may add.
Read the guide
Supplier oversight
How to manage suppliers, third-party components and software bills of materials for the EU Cyber Resilience Act, for UK product teams and buyers.
Read the guideHow CyPro can help
Need a hand getting ready?
Reading the rules is one job. Mapping them to your organisation, closing the gaps and showing the evidence are several more. CyPro's consultants can take any of them off your plate.
Fractional CISO for the board
A senior security lead who advises the board on what to fix first, what to accept and what to tell customers, and owns the decision record.
More on cypro.co.uk
Penetration testing
A focused test of your systems and the controls around them, so you know they hold before an attacker finds out for you.
More on cypro.co.uk
Hardening and segmentation
Our consultants put the controls in place that limit the damage when something is missed: firewall rules, network isolation and tighter admin access.
More on cypro.co.uk
24/7 security monitoring
Our SOC analysts watch your systems day and night for the signs of an attack in progress: unexpected processes, new outbound connections, logins that do not fit.
More on cypro.co.uk
Incident response
If you may already be compromised, our responders contain it, preserve the evidence, find out what was touched and get you running again safely.
More on cypro.co.uk
Vulnerability scanning
Find every internet-facing system you run, including the forgotten ones, and see which are still on a vulnerable build.
See the scanning service
Get ready
Need to know what this means for you?
Meeting the Act takes a named owner for product security, a decision path for reporting and a plan to 2027. A virtual CISO can take that role, assess which products are in scope and report progress to your board.