← All industries

Cybersecurity in mechanical engineeringWhen the machine becomes software

A modern machine is unthinkable without control software, an operator interface and remote access. That is exactly what brings it under the Cyber Resilience Act – and from 2027 the Machinery Regulation also requires the control system to be protected against cyberattacks.

01

The starting point

A mid-sized special machinery manufacturer delivers systems that stay in service for 20 years. The controller comes from a supplier, the HMI software has grown over years, remote maintenance runs through a third-party gateway. Nobody knows completely which software component in which version is installed where.

Under the CRA it is no longer enough that the machine works. The manufacturer must be able to prove which digital components are included, how vulnerabilities are handled and for how long security updates are provided – across the entire supply chain. Regulation (EU) 2023/1230 on machinery follows from January 2027: protecting the control system against manipulation then becomes part of machinery safety and thus of the technical file.

02

What is specifically required

Software bill of materials

A machine-readable SBOM of at least the top-level dependencies – including purchased controllers and modules.

Vulnerability handling over the lifetime

A process that detects, assesses and fixes known vulnerabilities – for machines that run for decades.

Reporting obligations

Actively exploited vulnerabilities and severe incidents must be reported within short deadlines.

Technical documentation for the CRA and the Machinery Regulation

Risk assessment, security measures and support period must be documented and available to market surveillance – from 2027 also as the cybersecurity part of the technical file under the Machinery Regulation.

03

How ProductShield helps

1Create the machine as a product with all digital components

Controller, HMI, firmware and remote maintenance gateway are recorded as assets of the machine – including supplier, version and owner.

Machine product with assigned assets
Machine product with assigned assets

2Merge supplier SBOMs

Bills of materials from controller and software suppliers are imported and merged into the machine's overall SBOM. Gaps become visible before a customer asks.

Merged SBOM across several suppliers
Merged SBOM across several suppliers

3Assess vulnerabilities and generate evidence

Known vulnerabilities are mapped to components, pre-assessed with AI support and documented with your decision. The CRA report summarises everything for the technical documentation and provides the cybersecurity part of the file under the Machinery Regulation.

Risk assessment and evidence per machine type
Risk assessment and evidence per machine type

The result

Instead of Excel lists per project there is traceable documentation per machine type – with version states, supplier components and support period. When a customer or market surveillance asks, the answer is an export, not a project – for the CRA as well as for the Machinery Regulation.

ProductShield supports technical structuring, risk analysis and documentation. A final legal assessment is not performed automatically and should be supplemented by specialised advisors or notified bodies where required.