News · 12 December 2024
The Cyber Resilience Act is in force: security as a product requirement
The EU Cyber Resilience Act (CRA) entered into force on 10 December 2024. It covers "products with digital elements": hardware and software that connects, directly or indirectly, to another device or network. Think routers, smart sensors, industrial gateways, mobile apps and embedded software.
A different kind of regulation
Many cybersecurity rules apply to operators of services. The CRA applies to manufacturers and, with differing duties, to importers and distributors. It asks them to design products with security built in, keep them secure through their support period, and handle vulnerabilities responsibly. Most obligations apply from December 2027; the duty to report actively exploited vulnerabilities and severe incidents applies earlier, from September 2026.
What manufacturers will need to do
- Perform a cybersecurity risk assessment and design accordingly.
- Ship with secure default configurations and a way to receive security updates.
- Maintain technical documentation, including a software bill of materials (SBOM).
- Run a vulnerability handling process: a contact point, timely fixes and coordinated disclosure.
- For most products, assess conformity themselves; for a smaller set of critical categories, involve a third party.
Open-source software gets particular treatment. Volunteers publishing code outside a commercial activity are not manufacturers, but companies that commercially integrate open-source components are responsible for the security of what they ship.
Why this matters for IoT and monitoring platforms
Connected sensors and gateways are classic CRA territory. A monitoring platform that collects data from field devices will inherit questions about update mechanisms, credential handling and what happens when a vendor stops supporting a component. We favour open-source foundations because transparency helps here, but openness does not remove the duty to keep components patched.
Starting early
The sensible first steps cost little: generate an SBOM for each product, define who receives vulnerability reports, and put a patching schedule in writing. Independent security testing then gives you evidence rather than assertion. Doing this in 2025 rather than 2027 means the regulation will arrive as a confirmation of habits you already have.
Written in December 2024; details reflect the situation at that time.