The Cyber Resilience Act and machine vision: what machine builders need to know
Until now, security in a vision cell was mostly a matter of the network: cameras in their own VLAN, cell offline, done. The EU Cyber Resilience Act turns it into a property of the product – with deadlines, documentation duties and fines.
In this post we explain what the CRA requires, which dates matter, what it means for a typical vision-guided robot cell, and what we at HD Vision Systems are doing to prepare our LumiScan apps. It is an overview from a manufacturer’s point of view, not legal advice.
What is the Cyber Resilience Act?
The CRA – Regulation (EU) 2024/2847 – sets mandatory cybersecurity requirements for “products with digital elements”: hardware and software made available on the EU market that can be connected, directly or indirectly, to a device or a network. That includes an industrial camera with firmware, a vision PC, standalone software such as a vision app – and the machine they end up in. As with product safety, cybersecurity becomes part of the CE marking.
The central idea: security is no longer a one-off check at release. Manufacturers must design products securely, ship them without known exploitable vulnerabilities, and keep fixing vulnerabilities for a defined support period.
The timeline
| Date | What applies |
|---|---|
| 10 December 2024 | The CRA enters into force. |
| 11 June 2026 | The rules for conformity assessment bodies (notified bodies) apply. |
| 11 September 2026 | Manufacturers must report actively exploited vulnerabilities and severe security incidents. |
| 11 December 2027 | All requirements apply. Products placed on the market from then on need CE marking under the CRA. |
The reporting obligations cover all products in scope – including those placed on the market before September 2026. Reports go to the Single Reporting Platform run by ENISA, in three stages: an early warning within 24 hours of becoming aware, a notification within 72 hours, and a final report – 14 days after a fix is available for a vulnerability, or one month after the notification for an incident. Violations can be fined up to €15 million or 2.5 % of worldwide annual turnover.
What manufacturers have to deliver
From December 2027, the main obligations are:
- Secure by design and by default. Products ship with a secure default configuration, protect their data and interfaces, and keep the attack surface small.
- No known exploitable vulnerabilities when the product is placed on the market.
- Vulnerability handling for a support period that reflects how long the product is expected to be in use – generally at least five years. Security updates have to be provided, as a rule free of charge.
- A software bill of materials (SBOM) in a common machine-readable format, covering at least the top-level dependencies, as part of the technical documentation.
- A coordinated vulnerability disclosure policy and a contact point where anyone can report vulnerabilities.
- Technical documentation, a conformity assessment and an EU declaration of conformity. Most products fall into the default category, where the manufacturer assesses conformity itself. Certain “important” and “critical” product categories listed in the regulation need harmonised standards or a third-party assessment.
Free, non-commercial open-source software is largely exempt. But anyone who builds open-source libraries into a commercial product is responsible for them as part of that product.
Who is responsible in a vision cell?
A typical vision-guided robot cell contains products from several manufacturers: a camera with firmware, lighting, vision software, an edge device or controller, a robot and a PLC. Each manufacturer carries the CRA obligations for its own product.
The machine builder or integrator who places the complete cell or machine on the market under their own name is a manufacturer too – of the machine. They have to exercise due diligence when integrating third-party components and ensure that these components do not compromise the security of the machine. In practice: if your vision supplier cannot tell you how long they will provide security updates, that becomes your problem.
At almost the same time, the new Machinery Regulation (EU) 2023/1230 applies from 20 January 2027. It adds its own requirements on protecting machinery control systems against corruption, including malicious attempts by third parties. Machine builders therefore have to deal with both regulations within a few months.
Questions to ask your vision supplier
Ask now – before you commit to components for machines you will still be selling after December 2027:
- Support period: How long will you provide security updates for this product, and when does that period start?
- SBOM: Can you provide a software bill of materials for the version you deliver?
- Update path: How do updates reach a cell that is not connected to the internet? Can security fixes be installed without changing functions?
- Security contact: Where do I report a vulnerability, and how will you inform me about one?
- Interfaces: Which interfaces are open by default, and can they be secured (encryption, authentication) or switched off?
Don’t forget the “hidden” software: camera firmware, drivers, runtimes and the libraries on the vision PC all count.
How we are preparing LumiScan
We develop our LumiScan apps for Windows 11, Ubuntu 24.04 and ctrlX OS ourselves, so the CRA obligations for this software are ours. This is where we stand:
- Clean, traceable builds. Our release packages are built and published only by our build pipeline, on clean, purpose-built build VMs – never on individual developer machines. Every release can be traced back to its source code, and nothing from a developer’s environment ends up in what we ship.
- An SBOM for every release. For each release we generate a software bill of materials in the standard formats SPDX and CycloneDX and keep it. It lists the transitive dependencies as well – more than the CRA’s minimum of top-level dependencies.
- Automated vulnerability scanning. A scheduled job in our build infrastructure regularly checks the SBOMs of all releases – including versions already in the field – against newly published vulnerabilities. That is how we can answer “is version X affected?” in minutes, not days.
- A dashboard for vulnerabilities and threats. The results flow into a dashboard on which we monitor the security status of our products and their dependencies and prioritise fixes.
- Licence compliance. The same job checks the licences of all third-party components, so that every open-source library we ship may be shipped the way we use it.
- Updates through established channels. On ctrlX OS, our apps are installed and updated through the ctrlX OS Store; on Windows and Ubuntu through our installers.
- Secured interfaces. For the OPC UA interface of LumiScan VGR, a security model with full encryption and authentication is on our roadmap, aligned with the OPC UA Companion Specification for Machine Vision (VDMA 40100).
- Lifecycle information for machine builders. We will publish the support periods of our products and a contact point for vulnerability reports, and provide the information machine builders need for their own technical documentation.
Frequently asked questions
Does the CRA apply to software that is sold on its own?
Yes. Standalone software is a product with digital elements in its own right – for example a vision app installed from an app store.
Do products that are already on the market have to comply?
The reporting obligations have applied to all products in scope since 11 September 2026, including older ones. The other requirements apply to products placed on the market from 11 December 2027, and to older products that are substantially modified after that date.
Is an offline cell exempt?
No. The CRA covers products that can be connected directly or indirectly, through a network or any other data connection. Network segmentation remains good practice, but it does not replace the product requirements.
Can a product be called “CRA compliant” today?
Be careful with such claims. The harmonised standards are still being finalised, and conformity is demonstrated through the conformity assessment and the EU declaration of conformity. Ask for concrete facts instead – support period, SBOM, update path and security contact.
Talk to us
The CRA is often seen as bureaucracy. For machine vision, we think it mainly puts into law what customers should expect anyway: a production cell runs for ten years or more, and the software in it has to be maintained for that long. If you are planning machines that will be placed on the market after December 2027 and want to know what we can provide for your documentation, get in touch.