
The Cyber Resilience Act: what a buyer can ask for
The Cyber Resilience Act was written for manufacturers, but buyers notice it first: on the box, in the documentation, and in the question of how long a device will keep getting security updates. You do not have to certify anything. You can, however, start buying better now, because what you buy this year will still be running in 2028.
The Cyber Resilience Act places its duties on manufacturers, importers and distributors, not on the organisation that buys and uses a product.
For buyers, the support period is the rule that matters most: how long a product receives security updates, with an end date the manufacturer has to state at the point of purchase.
Put the end date, the update policy, a vulnerability contact and an SBOM on request in your purchasing terms, and have the legal side reviewed by a lawyer.
What the Cyber Resilience Act covers, and who it applies to
The Cyber Resilience Act (Regulation (EU) 2024/2847) was published in 2024 and sets cybersecurity requirements for products with digital elements: hardware and software placed on the EU market. That includes laptops, switches, firewalls, printers, cameras, smart locks and standalone software, along with the firmware inside them.
The duties sit with manufacturers, importers and distributors. They have to design products securely, handle vulnerabilities, deliver updates and document all of it. The organisation that buys and uses the product gets no obligations of its own from this regulation.
Pure cloud services are largely outside its scope; NIS2 is the framework there. If your organisation falls under NIS2, the CRA still matters to you: NIS2 asks you to look at supply chain security, and the CRA gives you the vocabulary to make that concrete when you buy.
If you are in Great Britain, the CRA applies to what is placed on the EU market, not to the British one. The UK has its own regime for consumer connectable products, the PSTI Act, in force since April 2024. Many manufacturers sell the same models in both markets, so the CRA will still shape what you can buy.
The dates that count
- 2024: the regulation was published and entered into force. Manufacturers have had a transition period since.
- September 2026: the reporting obligations apply. Manufacturers must report actively exploited vulnerabilities and severe incidents through a single European reporting platform run by ENISA. According to the regulation, this also covers products placed on the market earlier.
- December 2027: full application. New products can then only be placed on the market if they meet the essential requirements, with a CE marking that partly rests on the CRA.
The gap in between is what matters most to buyers. Until the end of 2027, products never designed for the CRA sit on the shelf next to products that already are. You cannot tell them apart from the outside, and a switch you buy today will still be running in five years. So ask now.
The support period: the rule that affects buyers most
Under the CRA, a manufacturer has to set a support period: the time during which it handles vulnerabilities and delivers security updates. It should reflect how long the product is expected to be used and is, as a rule, at least five years, unless the product has a shorter life. The end date, as month and year, has to be clear at the point of purchase.
Security updates during that period have to be free of charge and, where technically feasible, separate from updates that add features. That helps in practice: you can close a hole without having to test a new version.
What to do with it: set the end date against your own depreciation and replacement cycle. A device you want to use for seven years whose support ends after five costs you two years of risk or an early replacement. Record the date in the asset register so that replacement is a plan rather than a surprise. How to run that whole cycle is covered in device lifecycle from purchase to disposal.
The Cyber Resilience Act in your purchasing terms
You do not have to wait for December 2027. You can put these points in a request for quotation or a framework agreement today, and a manufacturer that is preparing can answer them:
- End date of support, per model, with month and year. Not “for as long as the product is sold”.
- Update policy: how updates are delivered, whether security updates install automatically by default, and whether you can defer them to a maintenance window.
- A vulnerability contact: where a researcher or your administrator can report a flaw, and how the manufacturer publishes fixed vulnerabilities.
- Secure defaults: no shared default password, unnecessary services off, and a way to reset to factory settings.
- An SBOM on request (see below), for the products where it matters.
- After December 2027: the EU declaration of conformity and the CE marking on new products.
How to build requirements like these into a standing purchasing process rather than order by order is on our page about IT procurement and vendor management.
An SBOM: what it is and when to ask for one
An SBOM (software bill of materials) is the parts list of a piece of software: which libraries and components it contains, in which version. The CRA requires manufacturers to draw one up as part of their technical documentation. It does not require them to hand it to customers. If you want it, you have to ask, preferably in the contract.
Its value shows the day a vulnerability is announced in a widely used component. Without an SBOM you ask each supplier whether your devices contain it. With one, you look it up. Ask for a common format such as SPDX or CycloneDX, so you can load it into a tool rather than read it.
Do not ask for one for everything. Start with what faces the internet and what protects your network: firewalls, VPN equipment, access points, and software reachable from outside.
What you already have in place
The CRA does not apply retroactively to devices you already own: a printer bought in 2023 does not become subject to it. Two things do change. The manufacturer’s reporting obligation also covers older products, and “how much longer will this get updates?” becomes a normal question to ask.
- Make an inventory of the support end date per model, as far as the manufacturer states one.
- Treat devices without updates as a risk: replace them, or isolate them on their own network segment without internet access.
- Watch out if you become a manufacturer yourself. If you place a product on the market under your own name, or substantially modify a product and sell it on, you may fall under the manufacturer’s obligations. Whether that applies to you is a question for a lawyer.
Where our work stops
What we do. We supply and manage hardware and software from manufacturers. We request support periods and update policies, record end dates in the asset register, plan replacement, apply security updates and keep track of which devices no longer receive them. We are certified to ISO 9001 and ISO/IEC 27001, which describes how we work, not a verdict on any product.
What we do not do. We are not a manufacturer and not a lawyer. We do not draw up declarations of conformity, we do not assess whether a product complies with the Cyber Resilience Act, and we do not report vulnerabilities on a manufacturer’s behalf. What a manufacturer commits to is its own commitment. Whether your organisation falls under the manufacturer’s obligations, and how to put CRA requirements into a contract legally, is something to discuss with a lawyer.
Questions we get about this
The five that come up most often.
What is the Cyber Resilience Act?
The Cyber Resilience Act is an EU regulation from 2024 that sets cybersecurity requirements for hardware and software placed on the EU market. Manufacturers must design products securely, handle vulnerabilities and deliver security updates throughout a support period. Importers and distributors must check that this happens.
When does the Cyber Resilience Act come into force?
The regulation was published in 2024. The reporting obligations for manufacturers apply from September 2026, and full application follows in December 2027. From then on, new products can only be placed on the EU market if they meet its requirements.
Does the CRA apply to us if we only buy products?
If you only buy and use products, the CRA gives you no obligations of your own. You can, however, ask more of your suppliers, such as an end date for updates and a vulnerability contact. If you sell a product under your own name or substantially modify it, that may be different; ask a lawyer.
What is the support period under the CRA?
It is the period during which the manufacturer handles vulnerabilities and provides security updates free of charge. It should match the expected period of use and is, as a rule, at least five years unless the product has a shorter life. The end date should be clear when you buy.
Can you assess whether a product complies with the CRA?
No. We are not a manufacturer and not a lawyer, and we do not assess or certify whether a product complies with the Cyber Resilience Act. What we do is request support periods and update policies, record them in the asset register and plan replacement. Conformity is the manufacturer’s responsibility.
Further reading
Where this piece connects.
Shall we make your purchasing look at updates?
Send us your device list or your next order. We will look up how long each model receives security updates and what that means for your replacement plan.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.