Cyber Resilience Act for controllers and industry: am I affected?
4 min read
The Cyber Resilience Act does not only apply to consumer products. Controllers, sensors with a fieldbus, gateways and entire automation systems can fall under it too. This guide shows how manufacturers of industrial electronics can tell and how the Commission deals with long development cycles and old protocols.
When industrial electronics fall under the Cyber Resilience Act
What matters is whether the product has a direct or indirect logical or physical data connection to a device or network (Art. 2(1)). The wording makes no distinction between consumer and industrial products.
As an example of a physical connection, the Commission FAQ expressly mentions an industrial fieldbus such as PROFIBUS connecting a sensor to a programmable logic controller. According to the guidelines, a data connection exists where information is digitally encoded by a sender and read as data by a receiver. A signal that merely switches or supplies power without transmitting data is not enough.
Components placed on the market separately are also products with digital elements (Art. 3(1)) – for example a controller, a communication module or a circuit board that you supply to other manufacturers.
Source: Art. 2(1) CRA · Art. 3(1) CRA · Commission FAQ on the CRA, 1.3 · Commission guidance C/2026/6013, points 18, 26–28
Installations and complex systems
Where a system made up of several hardware and software parts is placed on the market as one product, it is a product with digital elements. According to the guidelines, long development cycles, old contracts and interoperability requirements do not take it out of scope – but they feed into the risk assessment.
One of the Commission's examples concerns older protocols: where a product must communicate with existing systems that only support an insecure protocol, the manufacturer may use it for that purpose – provided it mitigates the risks by other means, documents them and, where technically feasible, enables the secure protocol by default.
Where a function runs in the manufacturer's cloud – in the Commission's example an industrial robot whose gripping position is calculated by a cloud service from camera images – that service is part of the product as remote data processing.
Source: Art. 3(2) CRA · Commission guidance C/2026/6013, points 29–32, Example 10, Section 8.3.4
Products designed before the Cyber Resilience Act
A product type designed before 11 December 2027 but still placed on the market after that date does not automatically have to be redesigned. The manufacturer carries out a risk assessment. If it shows that the existing security measures are appropriate, the manufacturer may rely on them. It still needs a conformity assessment, an EU declaration of conformity and the CE marking.
Parts bought before the cut-off date may also be built in – the Commission mentions microcontrollers in an automation system. What matters is that the system as a whole meets the essential requirements. The due diligence obligation under Art. 13(5) applies to integrating third-party components in any case.
Source: Art. 13(5) CRA · Commission guidance C/2026/6013, points 33–36, Example 11
Which products face stricter checks
Annex III lists some categories that are common in industry. Stricter conformity assessment procedures apply to them:
- Class I: physical and virtual network interfaces, routers and switches, network management systems, microprocessors, microcontrollers, ASICs and FPGAs with security-related functionalities
- Class II: firewalls, intrusion detection and prevention systems, tamper-resistant microprocessors and microcontrollers
What matters is the core functionality of the product. Integrating a component from Annex III does not in itself make the whole product an important product (Art. 7(1)). Our guide on important and critical products describes all categories and procedures.
Source: Art. 7(1) CRA · Annex III, Classes I, II CRA
Machinery: the Machinery Regulation as well
Manufacturers of machinery or safety components must also meet the requirements of the Machinery Regulation on protection against corruption and on the safety of control systems from 20 January 2027. Both sets of rules apply side by side. Our guide on the Machinery Regulation explains what it requires and when.
Source: Annex III, points 1.1.9, 1.2.1 Machinery Regulation · Corrigendum to the Machinery Regulation, OJ L 169 of 4 July 2023 (application from 20 January 2027)
What applies from when
- Since 11 September 2026: reporting obligation for actively exploited vulnerabilities and severe incidents – including for products already on the market before (Art. 14, Art. 69(3), Art. 71(2)).
- From 11 December 2027: all other obligations (Art. 71(2)).
- Products placed on the market before 11 December 2027 only have to meet the requirements if they are substantially modified later (Art. 69(2)).
Source: Art. 14 CRA · Art. 69(2), (3) CRA · Art. 71(2) CRA
In practice
- Go through the product portfolio: which devices have a data connection – Ethernet, fieldbus, radio, USB?
- For product types that will still be sold after 11 December 2027, start the risk assessment now.
- Record bought-in parts and their support periods; ask suppliers about SBOMs and vulnerability handling.
- Organise the reporting obligation – it already applies today, including to installations in the field.
Related guides
Terms in the Cyber Resilience Act glossary
Sources
- Regulation (EU) 2024/2847, Art. 2, 3, 7, 13, 14, 69, 71, Annex III (EUR-Lex, Official Journal)
- Commission guidance C/2026/6013, OJ C, 17 Nov 2026, Sections 2.2–2.7 and 8.3.4 (non-binding)
- Commission FAQ on the Cyber Resilience Act, version 1.4 of 4 September 2026, 1.3
Status of the Commission guidance: the Commission approved its content on 27 July 2026 (C(2026) 5252). On 17 November 2026 the guidance was published in the Official Journal as Communication C/2026/6013, in all official languages. According to our comparison, the point numbers have not changed. The guidance is not binding, but it shows how the Commission reads the Regulation (as of 11/2026).
First published 31 Oct 2026, last updated 31 Oct 2026. This guide reflects the wording of the regulation and the Commission’s guidelines and does not constitute legal advice.