Cyber Resilience Act (CRA): what changes for your company
By Jorge Graells · November 3, 2026 · 5 min read
The Cyber Resilience Act requires makers of products with software to meet security requirements and, since 11 September 2026, to report actively exploited vulnerabilities within 24 hours. Importers and distributors are covered too.
Cyber Resilience Act (CRA): what changes for your company
- Type
- Article
- Author
- Jorge Graells
- Date
- Reading time
- 5 min read
- Subjects
Summary
The Cyber Resilience Act requires makers of products with software to meet security requirements and, since 11 September 2026, to report actively exploited vulnerabilities within 24 hours. Importers and distributors are covered too.
If your company makes a connected device, writes software that ships inside another product, or imports gadgets with wifi from outside Europe, there is a European regulation that concerns you, even if hardly anyone has read it. It is called the Cyber Resilience Act (CRA), and since 11 September 2026 part of its obligations has applied. This is what the European Commission1 says, explained for the people who have to comply with it or buy products covered by it, not for lawyers.
◢What is the Cyber Resilience Act?
It is Regulation (EU) 2024/2847. According to the Commission, it sets mandatory cybersecurity requirements for hardware and software sold in the European Union. It entered into force on 10 December 2024 and applies to "products with digital elements", the official name for almost anything that runs software: an IP camera, a router, an industrial controller, a mobile app, or a management program installed on a customer's computer.
Until now, the security of these products depended on the manufacturer's goodwill. The regulation makes it a condition for selling them in Europe, in the same way other requirements are shown with the CE marking.
◢Which products does it cover, and which not?
According to the official summary2, the regulation covers hardware and software products whose intended or reasonably foreseeable use includes a direct or indirect data connection to another device or a network. It also includes components placed on the market separately, and remote data processing solutions that the manufacturer designed and without which the product could not perform one of its functions.
Products that are not made available on the market, meaning not supplied in the course of a commercial activity, are out, and so are some products already covered by other EU legislation. The Commission points to recital 18 to explain when free and open-source software counts as made available. If your case is unclear, such as a web service or a custom app for a single client, do not assume anything: on 27 July 2026 the Commission published an implementation guide3 with 67 practical examples, aimed mainly at small businesses, on top of its existing FAQs.
◢Which two dates matter?
- ▹11 September 2026: the reporting obligations of Article 14 already apply.
- ▹11 December 2027: the rest of the main obligations apply.
According to the Commission summary, products already on the market before December 2027 fall under the other obligations only if they undergo a substantial modification after that date. The reporting obligations, however, apply to all products made available, including those already on sale.
◢What must a manufacturer report, and how fast?
Since 11 September, manufacturers must report actively exploited vulnerabilities and severe incidents that affect the security of their products. The Commission's reporting page4 sets these deadlines:
- ▹An early warning within 24 hours of becoming aware.
- ▹A full notification within 72 hours.
- ▹A final report no later than 14 days after a corrective measure is available, for an exploited vulnerability. For a severe incident, within a month of the 72-hour notification.
Everything is submitted once, through the single reporting platform run by ENISA, the EU cybersecurity agency, which the Commission says has been operational since 11 September. The notification goes to the CSIRT of the country where the manufacturer has its main establishment and, unless there are exceptional circumstances, to ENISA as well.
The Commission adds a detail for smaller firms: micro and small enterprises cannot be fined for missing the 24-hour deadline.
◢What if I only import or distribute other people's products?
You are not off the hook, although these duties arrive with the other main obligations in December 2027. The Commission summary says the importer, who places on the EU market products carrying the name or trademark of a manufacturer from outside, must check that the manufacturer has met its obligations, that the conformity assessment was carried out and that the product bears the CE marking. If not, it cannot put the product on the market.
The distributor, who sells the product without changing it, must also verify the CE marking and that the manufacturer and importer have done their part, including contact details, user instructions and the support period. Anyone who resells connected equipment to customers (installers, integrators, shops) should know this will stop being optional.
◢What changes if my company only buys these products?
If you only buy, the regulation puts no direct obligations on you, but it changes what you can ask for. According to the Commission, the manufacturer must set a support period, during which it has to handle vulnerabilities effectively, and the end date (month and year) must be clear at the time of purchase.
That is genuinely useful. When the attacks on European supermarket refrigeration hit the news, the manufacturers said most of the affected equipment was discontinued and no longer received updates. The regulation will not fix those old devices, but it does require new ones to say how long they will be looked after.
◢What to do now
If you make, import or distribute products with software:
- ▹Work out whether your products fall within the regulation. Start with the Commission's guide and FAQs.
- ▹Decide who in the company will receive the alert about an exploited vulnerability and how the early warning will go out within 24 hours. That is what the law already requires.
- ▹Ask your component and third-party software suppliers how they handle vulnerabilities. As a manufacturer, you answer for what you integrate.
If you only buy:
- ▹Before acquiring connected equipment (cameras, controllers, locks, industrial devices), ask until when it will get security updates.
- ▹Put that date in your equipment inventory, next to who installed it and who can reach it from outside. I have written elsewhere that attacks rarely come in through the server, but through whatever nobody was keeping track of.
Understanding what the rule demands of you, and what you can demand in return, is part of what I teach in my cybersecurity training for companies, designed for teams that are not technical.
Related documents
- News
Crédit Mutuel Arkéa cyberattack: attackers came in through a vendor
French bank Crédit Mutuel Arkéa suffered an attack that allowed fraudulent transfers from its own account. The attackers got in through a service provider's platform. What we know, what we don't and what to learn.
- Article
Device code phishing: what it is and how to stop it
Device code phishing tricks the victim into typing a code generated by the attacker into Microsoft’s real sign-in page. That gives the attacker access to their Microsoft 365 account without a password and without two-step verification getting in the way. Blocking that sign-in flow stops it.
- News
Claude Code leaks keys on GitHub: the settings.local.json problem
Claude Code's "don't ask again" option can save passwords and API keys in .claude/settings.local.json. Apiiro found 1,122 public copies on GitHub with secrets inside. What we know and what to do.