Machinery Regulation (EU) 2023/1230 requires manufacturers to address cybersecurity risks that could cause unsafe machine operation, with the regulation becoming mandatory on 20 January 2027 [S4].
Machines with a PLC, safety controller, firmware, HMI, gateway, mobile application, or remote-maintenance connection may need to satisfy both the Machinery Regulation and Cyber Resilience Act (EU) 2024/2847 [S4].
What the Machinery Regulation Changes for Machine Builders
The Machinery Regulation replaces Directive 2006/42/EC and adds cybersecurity to the essential health and safety requirements, rather than treating it as a separate IT-security workstream [S3].
Manufacturers must carry out cybersecurity risk assessments that identify where their systems can be exposed and how those exposures could affect safety [S1]. The starting question is concrete: can an attacker corrupt safety software, override control logic, or turn a digital compromise into a physical accident? [S4]
For a connected machine, the applicable technical obligations sit in Annex III, including section 1.1.9 on protection against corruption and section 1.2.1 concerning safety-related control systems [S4][S9]. The declaration of conformity must identify the regulations applied, including Machinery Regulation 2023/1230 and Cyber Resilience Act 2024/2847 where both apply [S3].
Cybersecurity as a Safety Requirement
Protection against corruption applies when connecting another device or enabling remote communication could create a dangerous situation, and relevant software and data must be identified and protected against accidental and intentional tampering [S4].
Safety-related software should therefore be treated as part of the machine's safety architecture. Examples include safety firmware, safety controllers, safety-critical signals, programmable control logic, and interfaces capable of influencing hazardous movements [S4]. External USB media, Wi-Fi links, maintenance laptops, gateways, and remote-access services can all become routes into that architecture [S7].
Legitimate and illegitimate interventions relevant to safety must be logged and traceable, which creates an engineering requirement for event capture, time reference, retention, and review rather than a simple firewall deployment [S4]. Cybersecurity threats must not be allowed to compromise the machine's safe operation under the Machinery Regulation [S5].
Choose Controls by Exposure and Safety Consequence

The correct control set depends on the machine's architecture, interfaces, operating environment, and the consequences of a digital failure, not on whether a product is marketed as an industrial IoT device [S4].
This comparison is not a prescribed control matrix. It is an engineering selection method that connects each interface to a threat, a protective measure, and evidence that can be audited during conformity assessment [S1][S4].
Machinery Regulation and Cyber Resilience Act Are Not Interchangeable
Machinery Regulation 2023/1230 asks whether digital interference can cause a physical accident, while Cyber Resilience Act 2024/2847 asks whether the product remains digitally secure throughout its life cycle, including vulnerability handling, software-component visibility, and post-market support [S4].
A machine can satisfy the Machinery Regulation's safety-focused cybersecurity duties and still fail the CRA's wider product-security obligations, so connected machinery must be assessed against both frameworks [S4]. For system-integration controls and supplier responsibilities, the IEC 62443-2-4 requirements for system integrators provide a useful engineering reference without replacing the legal assessment.
Who Needs the Full Cybersecurity Workstream

Machine builders and integrators should apply the full process when a product contains software, connects to a network, or permits remote access [S4]. The scope includes a PLC, safety controller, firmware, HMI, remote-maintenance connection, gateway, and mobile application used to control or monitor equipment [S4].
Manufacturers of connected safety functions have a particular exposure because a compromise can affect both machine availability and the controls intended to prevent hazardous movement [S5]. Producers that add software, communication modules, or remote services after delivery can also become relevant actors in the machine's cyber-risk chain [S4].
A standalone machine with no network, removable-media, or remote-control exposure may need a smaller set of controls, but it still needs an explicit assessment rather than an assumption that physical isolation removes every cybersecurity obligation [S1]. The assessment must cover accidental and intentional interference, including tampering with software and data [S4].
Build Evidence That Survives a Compliance Audit
A defensible conformity file links the hazard assessment, cybersecurity risk assessment, architecture, control configuration, and verification evidence. ABB identifies the risk assessment as the starting point for identifying where and how systems may be exposed [S1].
Relevant evidence can include an interface inventory, software and firmware baseline, component list, network-zone drawing, access-control matrix, signed-update process, event-log sample, penetration-test report, and supplier security commitment [S4][S8].
Designers should also record residual risk and the rationale for accepted control combinations. Protection against corruption must address both intentional and accidental tampering, while safety-related control systems require evidence that relevant interventions remain traceable [S4][S9]. Harmonized European standards can support legal interpretation and the presumption of conformity for the regulation they cover; the CRA had no harmonized standard when the November 2024 comparison was published [S3].
Common Failure Modes Before 20 January 2027

The most frequent technical weakness is treating the Machinery Regulation as an add-on IT questionnaire rather than as part of safety engineering, even though its cybersecurity provisions are embedded in Annex III [S3][S4]. Another failure is treating the CRA and Machinery Regulation as interchangeable compliance exercises [S4].
A second failure mode is securing the safety controller while leaving a service laptop, USB path, wireless interface, or supplier gateway outside the assessed boundary. A third is recording a firewall rule without testing whether logs reveal unauthorized safety-relevant interventions. A fourth is producing no controlled update path for firmware and third-party software components [S7][S8].
Safety functions based on machine learning also require a defined conformity route. Industry guidance published on 6 October 2026 states that EU machinery law treats cybersecurity as a safety requirement and places safety functions based on machine learning under mandatory third-party conformity assessment [S6]. This makes the algorithm's operating envelope, data assumptions, failure response, change-control process, and validation evidence part of the machine safety case.
Traceable Compliance from Risk Assessment to Release
The practical sequence is to freeze the machine's system boundary, map every external and maintenance interface to possible hazards, implement proportionate controls, test both cyber and safety effects, and retain evidence through production and service release [S1][S4].
Two trackable signals should be monitored before 20 January 2027: whether the final EU Declaration of Conformity names both Machinery Regulation 2023/1230 and Cyber Resilience Act 2024/2847 where applicable, and whether the technical file demonstrates vulnerability handling, software-component identification, protected safety controls, and traceable interventions [S3][S4].