← All industries

CRA for software vendorsKnow your dependencies, prove your releases

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.

01

The starting point

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.

02

What is specifically required

SBOM per release

A machine-readable bill of materials of direct dependencies belongs to every version placed on the market.

Coordinated vulnerability handling

Contact point, process and deadlines for reported vulnerabilities – including documentation of the decision.

Deliver security updates separately

Security updates should be available without functional changes, and users should be informed about them.

Name the support period

For every product it must be clear how long security updates will be provided.

03

How ProductShield helps

1Map product lines and releases

Each product line with its versions is created – with owners, support period and status.

Product line with release history
Product line with release history

2Take over SBOMs from the pipeline

The SBOM from the build is imported per release. Components with known vulnerabilities are flagged and presented for assessment.

Imported SBOM with flagged components
Imported SBOM with flagged components

3Document decisions and report

You decide whether a vulnerability is relevant – ProductShield records reasoning, measure and date and generates the CRA report from it.

Assessment history and report per release
Assessment history and report per release

The result

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.