← All industries

Cybersecurity for IoT and embeddedMany devices, many versions, one documentation

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.

01

The starting point

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.

02

What is specifically required

Secure default configuration

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.

SBOM per firmware version

Every shipped firmware version needs a traceable component list.

Update capability and support period

Security updates must be provided over the support period and users informed.

Cryptography in view

Cryptographic methods and libraries in use must be known – the basis for a CBOM.

03

How ProductShield helps

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.

Product family with variants and firmware versions
Product family with variants and firmware versions

2Maintain SBOM and CBOM per firmware

Components and cryptographic libraries are recorded per firmware version – imported from the build or added manually.

SBOM and CBOM of a firmware version
SBOM and CBOM of a firmware version

3Break vulnerabilities down to affected variants

A new vulnerability in the TLS stack immediately shows which variants and customers are affected. Assessment, decision and measure are documented.

Impact analysis across device variants
Impact analysis across device variants

The result

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.