1Map product lines and releases
Each product line with its versions is created – with owners, support period and status.
Software placed on the EU market falls under the Cyber Resilience Act – whether desktop, server or embedded. What matters is that you know your dependencies and handle vulnerabilities traceably.
A software company with 40 employees maintains three product lines in different technologies. Every release pulls hundreds of packages from npm, NuGet and Maven. Dependency scanning runs in the pipeline, but the results end up nowhere a customer or auditor could trace them.
Under the CRA the internal scan becomes a manufacturer obligation: SBOM per release, documented assessment of findings, reporting of actively exploited vulnerabilities and informing customers about security updates.
A machine-readable bill of materials of direct dependencies belongs to every version placed on the market.
Contact point, process and deadlines for reported vulnerabilities – including documentation of the decision.
Security updates should be available without functional changes, and users should be informed about them.
For every product it must be clear how long security updates will be provided.
Each product line with its versions is created – with owners, support period and status.
The SBOM from the build is imported per release. Components with known vulnerabilities are flagged and presented for assessment.
You decide whether a vulnerability is relevant – ProductShield records reasoning, measure and date and generates the CRA report from it.
A scan result in the pipeline becomes a traceable history per release: what was inside, what was found, how it was decided. That is exactly what customers with their own compliance obligations increasingly ask for.
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 →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 →