Does the EU Cyber Resilience Act apply to your product?

Marc HaddadForward Deployed Regulatory Engineer
The EU Cyber Resilience Act (CRA) applies to your product if it runs software and can exchange data with a device or network, directly or indirectly, and no Article 2 exclusion fits. Manufacturers have had to report actively exploited vulnerabilities and severe incidents since September 11, 2026, and everything else, including CE marking, applies from December 11, 2027.
Key points
- Scope: the CRA covers hardware, software, separately sold components and the backend a product relies on. Physical data links, such as a battery contact pin, count too.
- Reporting: required since September 11, 2026, for products already sold as well as new ones.
- Full application: from December 11, 2027, each unit placed on the EU market needs a conformity assessment, an EU declaration of conformity and CE marking.
- Conformity route: most products are self-assessed, while products in the Annex III and IV classes generally need a notified body or a certificate.
- Fines: breaching Article 13 or 14 can bring fines of up to EUR 15 million or 2.5% of worldwide annual turnover, whichever is higher.
What is the EU Cyber Resilience Act?
The Cyber Resilience Act is Regulation (EU) 2024/2847, the EU’s cybersecurity law for products with software or a data connection. It entered into force on December 10, 2024, and applies in full from December 11, 2027.
It is enforced by national market surveillance authorities, the bodies in each EU country that check products on sale. On July 27, 2026, the Commission published non-binding guidance, C(2026) 5252, covering scope, remote data processing, substantial modification and support periods.
Does the Cyber Resilience Act apply to my product?
Yes, if it is a “product with digital elements” and no exclusion fits. The term covers any software or hardware product together with its remote data processing solutions, including components placed on the market separately.[1]
The data connection can be logical or physical, direct or indirect.[1] A Bluetooth link to a phone counts, and so does a contact pin over which a battery pack exchanges data with a tool. Software placed on the market on its own, such as an app or separately sold firmware, is a product too.
Your backend is in scope if your product needs it. Remote data processing counts as part of the product when you designed the software for it and the product would lose one of its functions without it.[1] A hosted service with no product attached is different: it is a cloud computing service under NIS2, the EU’s network and information security directive, not a CRA product.[1]
Free products count too, because supplying a product free of charge in the course of a commercial activity still counts as making it available on the market.[1]
To map your scope, list every item with software (parts in the box, parts sold separately, apps and backends) and mark each data connection, including physical ones. The same habit helps when you work out which regulations apply to your product more broadly.
Which products are excluded from the CRA?
A few product groups regulated under other EU regimes are excluded, plus narrow cases for spare parts and defence. Knowing what product compliance covers helps explain why these other regimes sit outside the CRA. Test each possible exclusion against its article and record why it does or does not apply.
- Medical devices: medical devices and in vitro diagnostic devices under Regulations (EU) 2017/745 and 2017/746.[1]
- Vehicles: products covered by the vehicle general safety rules in Regulation (EU) 2019/2144.[1]
- Aviation: aviation products certified under Regulation (EU) 2018/1139.[1]
- Marine equipment: marine equipment under Directive 2014/90/EU.[1]
- Spare parts: spare parts that replace identical components and are made to the same specifications.[1]
- Defence: products developed or modified solely for national security or defence.[1]
The spare parts exclusion is narrow: a replacement battery pack with revised firmware is not identical, so it does not qualify. Aftermarket vehicle telematics units are an open question, because a unit that sits outside vehicle type approval is not clearly covered by Regulation 2019/2144.
Is my product “important” or “critical” under the CRA?
Only if its core functionality matches a category in Annex III (important products, split into Class I and Class II) or Annex IV (critical products). Products outside both lists take the simplest route.
Annex III lists 19 Class I categories and four Class II categories. Class I includes operating systems, password managers, internet routers and modems, microcontrollers with security-related functionalities, smart home security products, connected toys, and wearables that monitor health or are made for children. Class II includes firewalls and tamper-resistant microcontrollers. Annex IV lists three critical categories: hardware devices with security boxes, smart meter gateways, and smartcards and secure elements.
Implementing Regulation (EU) 2025/2392 of November 28, 2025, in force since December 21, 2025, gives the technical description of each category. It names smart door locks, for example.[2] Classify against those descriptions and write down your reasoning for every item you place outside the lists.
Core functionality decides: a gateway sold as an internet router is Class I, but one whose core functionality is relaying data from your own products is not. Building an important component, such as a secure microcontroller, into a host product does not make the host product important.[1] Nor does a certified radio module or Class I chip make your product compliant, because you are the manufacturer of the whole product.
When does the Cyber Resilience Act apply?
In stages: reporting has applied since September 11, 2026, and the full requirements apply from December 11, 2027.
- December 10, 2024: the CRA entered into force.
- June 11, 2026: the rules on notifying conformity assessment bodies started to apply.[1]
- September 11, 2026: reporting obligations started, for products already on the market as well as new ones.[1]
- December 11, 2026: Member States are to strive to have enough notified bodies by this date.[1]
- December 11, 2027: the CRA applies in full.
- June 11, 2028: EU-type examination certificates issued for cybersecurity requirements under other harmonisation legislation lapse, unless they expire earlier.[1]
From December 11, 2027, the requirements apply to each individual unit, not each model, when it is placed on the market.[1] Units placed on the market earlier stay outside unless they are substantially modified afterwards,[1] so plan SKU by SKU which units leave the factory before that date and which need the updated design.
After December 11, 2027, a firmware update can pull old units in, because a substantial modification after that date brings a product placed on the market earlier into scope.[1] A third party that makes such a modification and supplies the product becomes its manufacturer.[1]
Since August 1, 2025, Delegated Regulation (EU) 2022/30 has required internet-connected radio equipment to meet Article 3(3)(d), (e) and (f) of the Radio Equipment Directive (RED), so radio products already have cybersecurity rules. From December 11, 2027, the day the CRA takes over, Delegated Regulation (EU) 2026/339 repeals 2022/30.
What are the CRA reporting obligations?
Manufacturers must report actively exploited vulnerabilities (security flaws attackers are already using) and severe incidents for every product on the market. Reports go through the single reporting platform run by ENISA, the EU Agency for Cybersecurity, to the national CSIRTs (computer security incident response teams).
For an actively exploited vulnerability:[1]
- Early warning: send it within 24 hours of becoming aware of the vulnerability.
- Notification: send it within 72 hours.
- Final report: send it within 14 days after a fix is available.
Severe incidents follow the same first two steps, with a final report within one month of the notification.[1] You must also inform affected users.[1]
Third-party code counts, because Article 14(1) covers any actively exploited vulnerability contained in your product. You must also report a vulnerability you find in a third-party component to whoever maintains it.[1] Small companies are not exempt: microenterprises and small enterprises are spared fines only for missing the 24-hour early warning.[1]
Do you need a notified body for CRA conformity assessment?
Usually not. A notified body is an independent conformity assessment body designated by an EU country. Class I products need one unless they apply recognised standards or schemes in full, and Class II and critical products generally need a notified body or a certificate.[1]
- Outside the classes: internal control (module A), where you assess the product yourself.
- Class I: module A only if you apply harmonised standards, common specifications or a certification scheme at “substantial” level in full. Otherwise, EU-type examination followed by conformity to type (modules B and C), or full quality assurance (module H).
- Class II: modules B and C, module H, or a certification scheme.
- Annex IV: a European certificate where an Article 8(1) delegated act requires one; otherwise the Class II routes.
Harmonised standards give a “presumption of conformity”, meaning a product built to them is presumed to meet the requirements they cover. Standardisation request M/606 covers 41 standards that are still in development, and each gives that presumption only once its reference is cited in the Official Journal. Until a standard covering your category is cited, a Class I product needs a notified body unless it applies common specifications or a certification scheme at “substantial” level in full.[1] Check notified body capacity before you plan a Class I or II route.
The Regulation itself is fixed, but implementing acts, standards citations, guidance and national enforcement arrangements arrive one at a time, and any of them can change the answer for a product line. Daptic follows those acts and citations as they are published and works out which CRA requirements apply to each of your products in each EU market.
What do manufacturers have to do before December 2027?
Build the requirements into design, documentation and support now, so every unit shipped from December 11, 2027, conforms. Once you have mapped scope and class:
- Risk assessment: document the cybersecurity risk assessment.[1]
- Design and SBOM: design to Annex I Part I and keep a software bill of materials, a list of the software components in the product.[1]
- Component due diligence: apply due diligence to third-party and open-source components.[1]
- Support period: set a support period of at least five years, unless the product’s expected use is shorter.[1] Show the end date, at least month and year, at the time of purchase.[1]
- Security updates: keep each security update available for at least 10 years or for the rest of the support period, whichever is longer.[1]
- Conformity assessment: run the Article 32 procedure and compile the technical documentation.[1] Keep it for 10 years after the product is placed on the market, or for the support period if that is longer.[1]
- Declaration and CE marking: issue the EU declaration of conformity and affix the CE marking.[1] Brief your importer, who may place only conforming products on the market.[1]
How does the CRA treat open-source software?
Free and open-source software that is not monetised falls outside commercial activity,[1] and hosting code on an open repository does not count as making it available.[1] If you monetise it, you are its manufacturer.
Organisations that support open-source projects intended for commercial use on a sustained basis are “open-source software stewards”. Their regime is lighter: a documented cybersecurity policy,[1] reporting from December 11, 2027, and no administrative fines.[1] Free and open-source products in Annex III may use module A if their technical documentation is public.[1]
Example: applying the CRA to a cordless tool platform
Here is how the steps above play out for one product line. A brand owner outside the EU sells a professional cordless tool platform in the EU through its EU subsidiary, which acts as importer. The team first limited its CRA work to the drill. A review of the parts list then found four more products (separately sold battery packs, the charger, a free companion app and an LTE site gateway) plus a cloud fleet service that the drill’s theft lock and firmware updates depend on.
The table shows how each item came out.
| Item | Data connection | Annex III or IV? | Result |
|---|---|---|---|
| Drill with Bluetooth module | Wireless, to the phone | No: core functionality is drilling | Module A; RED Article 3(3) until December 11, 2027 |
| Battery pack | Physical, to tool and charger | No | Module A; packs sold on their own are products in their own right |
| Charger | Physical, to the pack | No | Module A |
| Companion app | Network | No | Module A, as a software product |
| Cloud fleet service | Remote data processing for the theft lock and updates | Not assessed separately | Part of the drill’s and app’s assessments |
| LTE site gateway | Network | Not if its core functionality is relaying tool data; Class I if it is a router or modem | Module A, or the Class I route |
The gateway was the hard call: its product page called it a “site router”, which opened up a Class I argument that the team then had to rebut in writing. Machinery, radio and electrical safety rules, the Batteries Regulation and data protection law also apply to this platform but sit outside this article.
Frequently asked questions
Can we keep shipping a model launched before 2027 unchanged?
No. Each unit placed on the EU market from December 11, 2027, must comply, whenever the model first launched.[1]
Do we need a notified body under the CRA?
Not for a product outside the Annex III and IV classes, which can use internal control. A Class I product needs one unless it applies harmonised standards, common specifications or a certification scheme in full.[1]
Is a smart door lock Class I under the CRA?
Yes, if its core functionality is protecting physical security in the home. Implementing Regulation 2025/2392 names smart door locks.[2]
Does an actively exploited flaw in an open-source library we ship need reporting?
Yes. Article 14(1) covers any actively exploited vulnerability contained in your product, and you must also report it to the library’s maintainer.[1]
What are the CRA reporting deadlines?
For an actively exploited vulnerability: an early warning within 24 hours of becoming aware of it, a notification within 72 hours and a final report within 14 days after a fix is available. Severe incidents follow the same first two steps, with a final report within one month of the notification.
Notes and sources
- Regulation (EU) 2024/2847 (Cyber Resilience Act), OJ L, November 20, 2024, particularly Articles 2, 3, 7(1), 13, 14, 19(1), 22(1), 24(1), 28, 30, 32, 35(2), 64, 69 and 71(2); recital 12; recital 38; Article 13(2) to (4); Annex I Part II, point 1; Article 31 and Annex VII; recital 18; recital 20.
- Commission Implementing Regulation (EU) 2025/2392, OJ L, December 1, 2025, particularly Annex I, item 17.
Additional sources:
- Commission Delegated Regulation (EU) 2026/339, OJ L, April 29, 2026
- Commission Delegated Regulation (EU) 2022/30 and Delegated Regulation (EU) 2023/2444
- Directive 2014/53/EU (Radio Equipment Directive)
- Commission guidance on the application of the CRA, C(2026) 5252, July 27, 2026
- European Commission, CRA policy page, reporting obligations and standardisation
- Proposal COM(2025) 837 (Digital Omnibus)
- Last reviewed: November 7, 2026.
This article reflects Marc Haddad’s independent opinions, not necessarily those of Daptic.



