← All industries

CRA for electronics manufacturersFrom component to firmware

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.

01

The starting point

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.

02

What is specifically required

Software transparency per assembly

SDKs, bootloaders, libraries: all software parts of an assembly must be known and documented.

Prove cryptography

Methods and crypto libraries in use belong in a CBOM – also with a view to future requirements.

Component and hardware lifecycle

Discontinued chips affect update capability and support period and must be recognised early.

Evidence for OEM supply

Customers need evidence they can take over into their own CRA documentation.

03

How ProductShield helps

1Record assemblies with hardware and software parts

Each assembly is created with microcontroller, SDK, bootloader and firmware versions – including the chip supplier.

Assembly with hardware and software assets
Assembly with hardware and software assets

2Maintain CBOM and SBOM together

Cryptographic libraries and methods are kept alongside software components. The hardware EOL check warns when a component is discontinued.

CBOM with crypto components and EOL notice
CBOM with crypto components and EOL notice

3Generate evidence per OEM customer

For each assembly a report with components, assessments and support period is created that your customers can reuse directly.

Report per assembly for OEM customers
Report per assembly for OEM customers

The result

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.