Skip to main content

This machinery cybersecurity checklist turns the cybersecurity requirements of the Machinery Regulation (EU) 2023/1230 into practical questions you can work through on your own machine.

From 20 January 2027, a machine whose safety functions can be altered through a network, a USB port or a remote link is not compliant, even if every guard and interlock works. The Machinery Regulation (EU) 2023/1230 makes protection against cyber threats part of machine safety. This checklist shows what to look at on your machine and what evidence to keep in the technical file.

The focus here is practical. For the regulatory background, including how the Cyber Resilience Act (CRA) applies alongside the Machinery Regulation and the key dates, see our article The Cyber Resilience Act and Machinery.

Where the Requirements Come From

Engineer using the HMI control panel of a CNC machine in a factory

Two essential health and safety requirements in Annex III of the Machinery Regulation drive the checklist:

  • 1.1.9 Protection against corruption: a connection to another device or a remote link must not create a hazardous situation. Safety-critical hardware, software and data must be identified and protected, and the machine must keep evidence of legitimate or illegitimate intervention.
  • 1.2.1 Safety and reliability of control systems: control systems must withstand reasonably foreseeable malicious attempts that could lead to a hazard, and safety-related software versions must be traceable.

The question is always the same: can someone, by accident or on purpose, change the machine’s safe behaviour through a digital route? If the answer is yes, the risk assessment must address it.

The Machinery Cybersecurity Checklist: What to Look At

Machine control cabinet with PLC, industrial Ethernet switch and port locks

Work through the machine as an attacker or a careless technician would. Each line below is a question your risk assessment should answer, with the evidence an assessor will expect to see.

# Area What to check Evidence to keep
1 Interfaces and access points Every route into the control system: Ethernet, fieldbus, USB, SD card, serial/service ports, Wi-Fi, Bluetooth, mobile modem, cloud gateway, HMI Interface list per machine type, with purpose and who may use it
2 Safety function independence Can a network message, HMI entry or PLC program change disable, bypass or alter an emergency stop, interlock, speed limit or safe torque off? Architecture drawing showing safety controller separation; analysis per safety function
3 Access control Default passwords, shared accounts, user levels on HMI and engineering software, physical locks on cabinets and ports User role matrix; proof that default credentials are changed or forced to change at commissioning
4 Remote access and maintenance Who can connect, how the connection is authorised, whether the operator on site must accept it, whether remote commands can start motion Remote access concept; encryption and authentication method; on-site enable procedure
5 Software integrity and updates Signed firmware, secure boot, checks that only approved safety software can be loaded, update procedure that keeps the machine in a safe state Update procedure; integrity mechanism description; version list of safety-related software
6 Safety parameters and configuration Can safety parameters (speeds, zones, muting, light curtain settings) be changed without authorisation? Are changes detected? Parameter protection method; checksum or signature records
7 Evidence of intervention Tracing log of interventions and of safety software versions uploaded after placing on the market; Annex III 1.2.1 requires this log to remain enabled for five years after each upload Log format, storage location, retention period; seals where digital logging is not reasonable
8 Wireless and radio controls Pairing, unique addressing, protection against replay or spoofing of start/stop commands, behaviour on signal loss Radio control specification; loss-of-signal test results
9 Third-party components PLCs, drives, HMIs, gateways and software libraries from suppliers: known vulnerabilities, support status, security documentation Component list or software bill of materials; supplier declarations
10 Reaction to detected corruption When an integrity check fails or an unexpected connection appears, does the machine go to or stay in a safe state? Test records of fault injection or simulated attacks
11 Information for use What the user must do: network segregation, password management, patching, disabling unused ports Instructions section on cybersecurity and the user’s responsibilities

A machine with no data connection and sealed service ports may need only a short justification. A connected machine with remote maintenance needs a documented analysis for every safety function that a digital route can reach.

Standards That Help

No single harmonised standard yet gives a presumption of conformity for 1.1.9 and 1.2.1. The documents below are the practical toolbox today.

Document What it gives you
prEN 50742, Safety of machinery: Protection against corruption (draft) Draft by CENELEC TC 44X, written for Annex III 1.1.9 and 1.2.1. Asset identification, threat analysis, security levels per safety function (SRSL 0–3), logging formats. Expected to be harmonised once published.
ISO/TR 22100-4 Guidance on IT security aspects for machine builders, linked to the EN ISO 12100 risk assessment
IEC TS 63074 Security aspects of safety-related control systems; bridges IEC 62061 and EN ISO 13849 with IEC 62443
IEC 62443-4-1, 62443-3-3, 62443-4-2 Secure development process, system requirements and component requirements; prEN 50742 accepts these as an alternative route
EN ISO 12100, EN ISO 13849-1, EN IEC 62061 The existing risk assessment and functional safety basis that cybersecurity analysis builds on

Note: prEN 50742 is still a draft standard. At the time of writing (October 2026) it is at the final approval stage and has not been published or cited in the Official Journal, so it does not yet give a presumption of conformity. Check its status before relying on it.

What to Put in the Technical File

  1. List of interfaces and digital components for each machine type.
  2. Cyber threats added to the risk assessment, linked to the safety functions they could affect.
  3. Protective measures chosen for each threat, with the standard or method used.
  4. Verification records: tests of access control, integrity checks and safe-state behaviour.
  5. Logging concept: what is recorded, where, and for how long.
  6. Version list of safety-related software and the controlled update procedure.
  7. Cybersecurity instructions for the user.

If the machine also falls under the CRA, keep the CRA cybersecurity risk assessment and software bill of materials in the same file, so both analyses use one consistent component list.

Common Mistakes

  • “Our machine is not online, so cybersecurity does not apply.” A USB port, a service laptop or a radio remote is also a digital route.
  • Relying only on the customer’s firewall. Network segregation at the user’s site helps, but the machine itself must resist foreseeable attempts.
  • Default passwords left in the HMI or PLC. One of the most frequent findings during assessment.
  • Safety parameters editable from the standard user level. Speed limits and safety zones need their own protection.
  • No record of software changes. Without version traceability, conformity cannot be shown after an update.
  • Treating the CRA and the Machinery Regulation as one exercise. The CRA protects the product; the Machinery Regulation protects people. Both analyses are needed.

How TESTPLUS Assesses Cyber-Related Safety

Conformity assessment expert reviewing the technical file with a machinery manufacturer

As Notified Body NB 2908 for machinery, TESTPLUS examines cyber-related requirements as part of the machine’s conformity assessment. We review the interface list, the extended risk assessment, the protection of safety functions and the logging concept against Annex III 1.1.9 and 1.2.1, and verify them on the machine where needed.

Planning to place connected machinery on the EU or Turkish market? Contact TESTPLUS to discuss the conformity assessment route for your machine. For background, see our articles on the Notified Body under the Machinery Regulation (EU) 2023/1230 and our Machine CE Certificate page.

The full legal text of the Machinery Regulation is available on EUR-Lex: Regulation (EU) 2023/1230.

Related reading