If you sell software, or devices and machines that contain software and connect to a network, the Cyber Resilience Act brings new obligations. From 11 December 2027, the CRA, Regulation (EU) 2024/2847, requires such products to be developed securely, supplied with security updates for years and given a CE marking before they are sold (Art. 13 and 71 CRA).
One obligation already applies today. Since 11 September 2026, manufacturers send an early warning within 24 hours when attackers demonstrably exploit a vulnerability in their product or a severe incident hits the product (Art. 14 CRA). This article shows step by step whether the CRA affects you, what it requires and where to start.
Does the Cyber Resilience Act apply to me?
The CRA covers products with two features. They are software or contain software, and they can connect to another device or a network, by cable, radio or the internet (Art. 2(1) and Art. 3(1) CRA). In addition, the product is offered in the EU as part of a commercial activity, for money or free of charge (Art. 3(22)).
Typical examples:
- A machine with control software that your service team accesses via remote maintenance.
- A measuring device or sensor that sends data to a computer by radio or cable.
- A desktop or mobile app that you sell or offer free of charge.
- Firmware or a software component that you supply to other manufacturers.
- The cloud application you develop for your device, without which the device loses a function, such as remote control (Art. 3(2)).
A manufacturer is anyone who develops such a product, or has it developed, and markets it under their own name or trademark (Art. 3(13)).
Machines with controls and remote maintenance
The exclusions in Art. 2 CRA do not mention machines. If a machine falls under the Machinery Regulation (EU) 2023/1230 and is also a product with digital elements, it has to meet both regulations. The work done for the CRA can make it easier to demonstrate conformity under the Machinery Regulation, for example for protecting the control system against tampering. The conformity assessment, meaning the check of all requirements, still follows both regulations (Recital 53 CRA).
Choose bought-in parts with software with care, such as a controller or software libraries, free open-source ones included. Integrate them so that they do not weaken the security of your product (Art. 13(5)).
The Cyber Resilience Act and software
For the CRA, standalone software is as much a product as a device, a free app included (Art. 3(1) and (22)). An online service that does not belong to one of your products is not covered by the CRA (Recital 12).
Which products does the CRA regulation not cover?
A device that cannot connect to anything, neither by cable nor by radio, is not covered (Art. 2(1)). Areas with their own rules are also excluded, such as medical devices, motor vehicles, marine equipment and products for defence (Art. 2(2) to (7)). Open-source software only counts if it is made available as part of a commercial activity (Recitals 15 and 18).
What is the Cyber Resilience Act?
The CRA is an EU regulation on the cybersecurity of software and connected devices, in force since 10 December 2024 (Art. 71(1)). You can find the text on EUR-Lex under number 2024/2847.
The deadlines are staggered:
- Since 11 September 2026, the reporting obligations apply, also to products you have already sold (Art. 14 and Art. 69(3)).
- From 11 December 2027, all other obligations apply to products you place on the market from that day, meaning make available on the EU market for the first time (Art. 71(2)).
- Older products only have to meet the other obligations if you substantially modify them after 11 December 2027 (Art. 69(2)).
For devices and machines, every single unit counts: a machine of a proven type delivered from 11 December 2027 needs the full proof, though not necessarily a redesign. For software, all copies of an unchanged version count as placed on the market with the first offer. This is set out in the draft Commission guidance of 27 July 2026 (C(2026) 5252, paras. 11, 13 and 33 to 38). This guidance will only apply once formally adopted in all official languages, and even then it is not binding.
As of 16 November 2026, no legal act has moved these dates. All dates with the related tasks are in our checklist on CRA reporting obligations and deadlines.
CRA requirements for manufacturers
For products placed on the market from 11 December 2027, Art. 13 essentially requires the following:
- Develop securely: the product meets the requirements of Annex I and is placed on the market without known exploitable vulnerabilities (Art. 13(1) and Annex I).
- Assess risks: you record which attacks are conceivable and how you protect against them (Art. 13(2) to (4)).
- Know the components: you keep a software bill of materials, the SBOM (Annex I, Part II, point 1).
- Close vulnerabilities: you provide security updates without delay and free of charge (Annex I, Part II, points 2 and 8).
- Support period: this is how long you deal with vulnerabilities, at least five years, shorter only if the expected use time is shorter. You state the end date at the time of purchase (Art. 13(8) and (19)).
- Be reachable: you name a contact point for reports of vulnerabilities and set out how you handle them (Art. 13(8) and (17)).
- Prove it: before the sale you draw up the technical documentation, meaning the documents on design and security, assess conformity, issue the EU declaration of conformity and affix the CE marking. With the declaration you take responsibility for your product (Art. 13(12) and Art. 28(4)).
On top of this comes the reporting obligation under Art. 14, which already applies. Who in your company reports and where is explained in CRA reporting obligations and deadlines to 2027.
What an SBOM is, how much effort it takes and what to arrange is covered in How to create an SBOM with CycloneDX and SPDX.
Self-assessment or notified body?
For most products, you check yourself whether they meet the requirements. You only need a notified body, a testing organisation designated by the state, for products on two lists in the annexes. Classification follows the core function; machines are on neither list, and an integrated router does not make your product an important product itself (Art. 7(1), Annexes III and IV).
Four levels:
- Default products that are on neither list: self-assessment in an internal procedure (Art. 32(1)).
- Class I, for example password managers, operating systems, routers and internet-connected toys that can talk, film or locate: self-assessment only with a harmonised standard, meaning a European standard published in the Official Journal of the EU, or an equivalent basis; otherwise a notified body checks (Art. 32(2)).
- Class II, for example firewalls and hypervisors: always a notified body or a European certification (Art. 32(3)).
- Critical products, for example smart meter gateways and smartcards: the Commission may require a European certification but had not done so by 16 November 2026. Until then, the same applies as for class II (Art. 8(1) and Art. 32(4)).
The harmonised standards for the CRA are still being drafted; on 10 November 2026 the Commission extended the deadlines for all product-specific and some general standards by three months. For class I, check whether a standard for your category is already in the Official Journal. Small and medium-sized enterprises pay reduced fees at notified bodies (Art. 32(6)).
Does the EU CRA apply to small companies?
Yes. Microenterprises and small enterprises are not exempt from the obligations; the support period of at least five years applies to them as well (Art. 13(8)). There are two reliefs:
- They may submit the technical documentation in a simplified form, using a form that the Commission lays down. As of 16 November 2026 it has not been published (Art. 33(5)).
- If they miss the 24-hour early warning, no fine is imposed (Art. 64(10)). How far this reaches is not clear from the wording; the notification and the final report remain mandatory.
Manufacturers based in Switzerland
What matters is whether your product is made available in the EU (Art. 2(1)). If you sell from Switzerland into the EU, the obligations apply to you too. Reports then go to the CSIRT where your authorised representative in the EU is based, otherwise where your importer or distributor is based (Art. 14(7) and Art. 18).
Penalties
The maximum amounts are staggered by obligation. For breaches of the security requirements and the obligations in Art. 13 and 14, they are up to 15 million euros or 2.5 percent of worldwide annual turnover, whichever is higher (Art. 64(2)). The member states lay down the detailed rules and also take the size of the company into account (Art. 64(1) and (5)).
Where to start
The CRA sets no separate deadlines for this preparatory work. The order is our recommendation and starts with what the reporting obligation already in force needs:
- Find out which products contain software and can connect.
- Decide who in your company reports via the ENISA platform and who stands in.
- Classify each product: default, class I, class II or critical.
- Have an SBOM created for each product and checked regularly for new vulnerabilities.
- Set the support period and start the technical documentation.
The detailed list with the legal deadlines is in the CRA checklist to 2027.
Note: this article summarises the regulation and the draft Commission guidance as of 16 November 2026. It is not legal advice. Whether your product falls under the CRA and into which class is for you as the manufacturer to decide; you issue the EU declaration of conformity yourself (Art. 28(4)).
SBOM and vulnerability monitoring as a service
The bill of materials and the check for new vulnerabilities stay with your product for the whole support period. We are building this technical part as a service: we create the SBOM of your product, check it every month against public vulnerability databases and send you a short report with an update recommendation. We chose the monthly rhythm; the CRA does not prescribe one. Classification, reports and the declaration of conformity remain with you.
The service is in preparation. Those who sign up hear first when it launches and what it costs: waiting list for the SBOM and vulnerability service.