1Record assemblies with hardware and software parts
Each assembly is created with microcontroller, SDK, bootloader and firmware versions – including the chip supplier.
Anyone manufacturing assemblies or devices with microcontrollers, firmware and interfaces places products with digital elements on the market. The Cyber Resilience Act requires transparency about software and cryptographic building blocks – even when they come from the chip supplier.
An electronics manufacturer develops assemblies that end up in devices of several OEM customers. The microcontroller comes with an SDK from the chip vendor, the bootloader stems from a reference design, the crypto library was integrated years ago and never touched again.
OEM customers now ask for SBOM, support period and vulnerability process – because they themselves are subject to the CRA. Without a clean overview per assembly and firmware version, every request becomes a scavenger hunt.
SDKs, bootloaders, libraries: all software parts of an assembly must be known and documented.
Methods and crypto libraries in use belong in a CBOM – also with a view to future requirements.
Discontinued chips affect update capability and support period and must be recognised early.
Customers need evidence they can take over into their own CRA documentation.
Each assembly is created with microcontroller, SDK, bootloader and firmware versions – including the chip supplier.
Cryptographic libraries and methods are kept alongside software components. The hardware EOL check warns when a component is discontinued.
For each assembly a report with components, assessments and support period is created that your customers can reuse directly.
You answer OEM requests with an export instead of research – and recognise early when a discontinued chip or an old crypto library threatens your support commitment.
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 →Firmware, radio modules, cloud connectivity: connected devices are at the core of the CRA and the Radio Equipment Directive – with many variants and long lifecycles.
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 →Controllers, SCADA and industrial IoT run for decades in critical plants. The CRA classifies many of them as important products.
View industry →