The Cyber Resilience Act (CRA), Regulation (EU) 2024/2847, is the EU law that sets mandatory cybersecurity requirements for products with digital elements, meaning hardware or software that can connect, directly or indirectly, to a device or a network. A packaging machine with a PLC, an HMI panel and an Ethernet port for remote support fits that description. For machine builders and PLC programmers, cybersecurity stops being a nice-to-have in the offer and becomes a condition for CE marking. That covers how you design it, how you document it and how you maintain it after delivery.
This guide explains what the regulation asks of you and when it applies. It closes with a step-by-step procedure you can start in your own workshop this month.
In particolar modo vedremo:
Key dates: what already applies and what is coming
The CRA entered into force on 10 December 2024 and applies in stages. Article 71 sets the dates.
| Date | What applies | Impact on a machine builder |
|---|---|---|
| 11 June 2026 | Rules on notifying conformity assessment bodies (Chapter IV) | Notified bodies can start being designated. This matters only if your product falls into a category that needs third-party assessment. |
| 11 September 2026 | Reporting obligations (Article 14) | Actively exploited vulnerabilities and severe incidents must be reported. This also applies to machines already on the market (Article 69(3)). |
| 11 December 2027 | All other obligations | Every new machine with digital elements placed on the EU market must meet Annex I, carry full technical documentation and bear the CE marking under the CRA as well. |
| 20 January 2027 | Machinery Regulation (EU) 2023/1230 (a separate law) | Adds its own requirements on protection against corruption of control systems. Plan both regulations together. |
The reporting obligation is already in force today. If a machine you sold in 2023 has a remote-access router that attackers are actively exploiting, you have to notify it.
Who is the “manufacturer” when you build a machine
The CRA assigns obligations by role. The machine builder who places the finished machine on the market under its own name is the manufacturer of that product. The PLC, the switch and the HMI come from your suppliers, and each of them is the manufacturer of its own component. Article 13(5) says you must apply due diligence when you integrate third-party components, so that they do not compromise the security of your machine.
| Role | Typical example | Main obligations |
|---|---|---|
| Manufacturer | Machine builder, PLC vendor, HMI software house | Annex I requirements, risk assessment, technical documentation, conformity assessment, vulnerability handling, reporting, support period |
| Importer | Company bringing a non-EU machine into the EU | Checks that the manufacturer has done its job and keeps documentation available |
| Distributor | Reseller of automation components | Checks the CE marking and documentation, and acts if it learns of non-conformity |
| Substantial modifier | Integrator who changes the security behaviour of a machine already on the market | Becomes the manufacturer for the modified product |
The last row matters to maintenance technicians and system integrators. A retrofit that adds remote connectivity, or replaces the control system, can count as a substantial modification. In that case the CRA obligations fall on whoever carried out the work.
What the essential requirements mean on a PLC project
Annex I has two parts. Part I covers properties of the product. Part II covers how you handle vulnerabilities during its life. Here is how they translate into everyday automation work:
- No known exploitable vulnerabilities at delivery. Check the firmware of the PLC, drives, HMI and router against the vendors’ security advisories before shipment.
- Secure by default configuration. No default passwords on the HMI or the web server of the CPU. Unused services (FTP, Telnet, unused web server, SNMP v1) must be off.
- Protection against unauthorised access. Enable the CPU access levels, protect project and know-how, and use separate user accounts on the HMI.
- Integrity and confidentiality. Use signed firmware where available, encrypted protocols for remote access and integrity checks on recipes.
- Minimised attack surface. Segment the machine network and expose only the ports you need.
- Logging. Record access and changes to program and parameters, where the hardware allows it.
- Security updates. You need a way to deliver patches, and the customer must be able to tell which version is installed.
- SBOM. Keep a software bill of materials covering at least the top-level dependencies in your technical documentation. You do not have to publish it.
You must also declare a support period. That is how long you commit to handling vulnerabilities. Under Article 13(8) it is at least five years, unless the product is expected to be used for less time. Industrial machines often run for twenty years, so expect to justify a period longer than five.
Practical procedure: from offer to after-sales
An invented example runs through the steps. Officine Valtorta Srl builds palletisers with a PLC, a 10-inch HMI and a 4G router for remote assistance.
- Check scope. List every machine model with a data connection (Ethernet, fieldbus to the plant, USB, wireless, remote router). Officine Valtorta finds that all three of its models are in scope.
- Classify. Check whether the product falls into the important (Annex III, classes I and II) or critical (Annex IV) categories. Most complete machines fall in the default category and can use self-assessment (module A). Some components they contain, such as routers or firewalls, are listed products, and you should ask the supplier for their CRA evidence.
- Inventory components and software. Record the brand, model and firmware version of every digital device. Officine Valtorta builds a spreadsheet per machine. From it they generate the SBOM and the list of security advisories to monitor.
- Assess cybersecurity risk. Do this alongside the safety risk assessment. Many builders use IEC 62443-3-2 and 4-1 as a method. They are not automatically a presumption of conformity with the CRA until harmonised standards are cited in the Official Journal, so check the status before relying on them.
- Harden the standard configuration. Write an internal checklist and apply it to every machine: passwords changed, services disabled, CPU protection active, remote access through a VPN with individual accounts.
- Set up vulnerability handling. Publish a security contact, write a coordinated disclosure policy and run a periodic check of supplier advisories. Assign someone named to the role, even part-time.
- Prepare for reporting. For an actively exploited vulnerability, you send an early warning within 24 hours, a notification within 72 hours and a final report within 14 days of a fix becoming available. Severe incidents follow the same 24 h / 72 h steps, with a final report within one month. Reports go to the CSIRT designated as coordinator in your Member State, through the single reporting platform managed by ENISA (Article 16). In Italy the national CSIRT is CSIRT Italia, part of ACN.
- Write the technical documentation and user information. This covers the risk assessment, the SBOM, test results, the support period, secure installation instructions and how to receive updates (Annex II and Annex VII).
- Issue the EU declaration of conformity and the CE marking. From 11 December 2027 the declaration also lists the CRA alongside the other applicable legislation.
- Maintain after delivery. Deliver patches for the whole support period and keep the documentation for ten years, or for the support period if that is longer.
Official documents to download
- Full text of the CRA, available in every EU language: Regulation (EU) 2024/2847 on EUR-Lex
- Machinery Regulation: Regulation (EU) 2023/1230 on EUR-Lex
- The European Commission’s CRA pages, which publish guidance, implementing acts and the status of harmonised standards.
Penalties are significant. Under Article 64, breaching the essential requirements can cost up to €15 million or 2.5% of worldwide annual turnover, whichever is higher.
Frequently asked questions (FAQ)
Do I need to update machines I delivered before December 2027?
Not to bring them into full conformity. Products placed on the market before 11 December 2027 are only subject to the full regime if they are substantially modified afterwards. The reporting obligations are different: since 11 September 2026 they also cover products already in the field.
Is a machine with no internet connection excluded?
Not automatically. The definition also covers indirect connections, such as a PLC on a plant network, a programming port or USB. A purely electromechanical machine with no programmable logic is outside scope.
The PLC vendor is already CRA compliant: am I covered?
Only for that component. You are still responsible for the machine as a whole: how you configure the PLC, the network architecture, remote access and your own PLC code.
Is IEC 62443 enough to comply?
It is a solid technical base and much of it lines up with Annex I. A legal presumption of conformity, however, only comes from harmonised standards whose references are published in the Official Journal. Check their status before your project is finalised.

Alessandro Strongoli has been programming PLCs and commissioning machines and plants for many years: S7-1200/S7-1500 with TIA Portal, WinCC panels, SINAMICS drives. Writing here since 2021. About the author


