1Structure device families and variants
Hardware revisions, firmware branches and companion apps are mapped as products and versions instead of staying hidden in file names.
Connected devices are at the centre of the Cyber Resilience Act, and radio equipment has been subject to the cybersecurity requirements of the Radio Equipment Directive (RED) since August 2025. Anyone shipping firmware, radio modules and cloud connectivity in series needs an overview of every variant – from chip to app.
A manufacturer of wireless sensors has 14 device variants in the field, three firmware branches and a cloud through which updates are rolled out. The radio module comes from a supplier, the TLS stack from an open source project, the app from an agency.
Under the CRA the manufacturer must be able to say for each variant which components are included, how long updates will be provided and how a vulnerability in the TLS stack will be fixed in the field – documented, not just in the head of the development lead.
No universal default passwords, secure updates, minimal attack surface out of the box – under the CRA and, for radio equipment, already today under the RED.
Every shipped firmware version needs a traceable component list.
Security updates must be provided over the support period and users informed.
Cryptographic methods and libraries in use must be known – the basis for a CBOM.
Hardware revisions, firmware branches and companion apps are mapped as products and versions instead of staying hidden in file names.
Components and cryptographic libraries are recorded per firmware version – imported from the build or added manually.
A new vulnerability in the TLS stack immediately shows which variants and customers are affected. Assessment, decision and measure are documented.
You know per variant what is inside, how long you owe updates and what to do at the next vulnerability. Hardware EOL check and lifecycle documentation turn the support promise into reliable planning.
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.
Machines with controllers, HMIs and remote maintenance are products with digital elements – the CRA and the Machinery Regulation require evidence for them.
View industry →Standard software lives on third-party libraries. The CRA requires you to know these dependencies and keep them under control.
View industry →Cloud services that provide functions of a product fall under the CRA too. We help draw the line cleanly.
View industry →Assemblies with microcontrollers and firmware, components from suppliers, crypto in hardware: the CRA reaches down to the board.
View industry →Controllers, SCADA and industrial IoT run for decades in critical plants. The CRA classifies many of them as important products.
View industry →