Headquarters South Africa
Beckhoff Automation (Pty) Ltd

7 Ateljee Street
Randpark Ridge, Randburg
Gauteng
2169, South Africa

+27 11 795 2898
info@beckhoff.co.za
www.beckhoff.com/en-za/

Oct 6, 2026

“PC-based control is an architectural benefit”

Torsten Förder, Product Compliance Security, Beckhoff Automation
Torsten Förder, Product Compliance Security, Beckhoff Automation

The Cyber Resilience Act has been in force since December 10, 2024 and will become fully applicable from December 11, 2027. Between those two dates, there is a lot of work for machine and system engineering companies to do. Three key questions about transforming CRA compliance from a cost driver into a manageable routine.

As a machine builder, is it enough to simply purchase CRA-compliant components?

Torsten Förder: No, that’s not how it works. What’s more, a product can still achieve conformity with the CRA even if it has components that do not demonstrate conformity installed in it. The benchmark is always the overall risk of the specific product, and each distributor is personally responsible for this. There are four tasks to be completed: implementing the CRA requirements based on an individual risk assessment, undergoing the conformity assessment process, establishing a vulnerability management system, and fulfilling the reporting obligations.

When it comes to the risk assessment, a good way to start is to try to view your own machine as an attacker would. Review the plans, walk around the facility, and look for doors that aren’t properly secured or possible ways to get inside. You don’t need a security expert for that – it’s just a shift in perspective. Of course, data communication is the gateway of choice these days.

How can machine builders keep the effort involved to a minimum?

Torsten Förder: The greatest leverage lies in the system design. Every component that falls within the scope of vulnerability monitoring incurs ongoing costs – so it should be removed from that scope wherever it is technically justifiable to do so without compromising cybersecurity. All interactions with the system can be routed through one or more gateways, and cross-system connections can be moved to dedicated lines with physical or cryptographic protection. This clearly separates “inside” and “outside.”

The attack surface is thus reduced to the gateways and well-protected cross-connections. It is then only these gateways and cross-connections that require risk assessments and organizational processes to monitor and fix any vulnerabilities. The number of components to be monitored is reduced – and with it the number and impact of updates to be provided for the field later on.

A second factor concerns the operator: Especially in the case of systems with professional operating personnel, the risk of internal manipulation can be effectively mitigated through organizational measures. Beware of going too far in the opposite direction, though: Overcompliance with standards for risks that are merely theoretical generates costs and complexity without delivering any measurable improvement in security. There is even a risk that, due to the mechanical application of standards and the absence of a proper threat analysis, the actual vulnerabilities will be overlooked – vulnerabilities that would have been identified during a pragmatic mental walkthrough of the system’s communication links.

From a technical perspective, what are the main benefits of PC-based control and EtherCAT?

Torsten Förder: PC-based control is an architectural benefit here, not a marketing tool. Unlike devices traditionally developed for programmable logic control, PC-based control technology benefits directly from the enhancements and updates to the underlying operating systems – and thus from the latest cybersecurity technology – without the need for parallel development.

Then there’s EtherCAT: The real-time Ethernet standard does not use the Internet Protocol. Malware, on the other hand, almost always relies on IP-based communication at Layer 3 of the ISO/OSI model – and it is precisely this switched layer that is not used for transporting EtherCAT payload data. This means that many attack scenarios familiar to those in the IT world are impossible from the outset. In addition, EtherCAT has relied from the very beginning on dedicated chips that handle network communication and provide hardware-based access protection. EtherCAT is, therefore, “secure by design” in the literal sense. EtherCAT technology can be used without any extensions to withstand an attack severity corresponding to Security Level 2 as defined in IEC 62443-3-3.

In practice, the two aspects are intertwined: A physical or virtual PC acts as a gateway, handling all communication with the environment – HMI, OPC UA server, and remote maintenance via SSH. The internal PC remains focused on the real-time application: static and without an attack surface.