EU Cyber Resilience Act

CRA compliance evidence, release by release

The CRA asks manufacturers to document the components in every product, handle vulnerabilities for the whole support period and report actively exploited ones within 24 hours. SBOMBox keeps that evidence per release, so the technical file and the reporting clock are both workable.

The problem

What makes this hard today

How SBOMBox helps

Evidence, not just a file

Generate SBOMs where your code lives

The sbombox CLI and CI action generate CycloneDX or SPDX SBOMs in your environment. Only the SBOM and its provenance are uploaded, never source code.

Score every SBOM at requirement level

Each upload is validated and scored against BSI TR-03183-2, CISA, NTIA and CRA readiness checks, with each requirement shown as pass, partial or missing.

Monitor for new vulnerabilities

Stored SBOMs are matched against OSV, GitHub Security Advisories, NVD and CISA KEV, so a newly exploited component shows up against the releases that contain it.

Record VEX decisions

Mark findings as not affected, affected, fixed or under investigation, with a justification, and keep that decision with the release it applies to.

Keep signed, per-release history

Every release's SBOM is stored immutably with its score and findings, so you can show what shipped in a version from two years ago.

Track the CRA reporting clock

The CRA workspace tracks early-warning, notification and final-report deadlines for actively exploited vulnerabilities, alongside support periods and stale evidence.

Getting started

How teams roll it out

  1. List your productsCreate one project per independently released product or firmware unit.
  2. Generate in CIAdd the CLI or CI action so every release produces a scored SBOM.
  3. Fix the gapsWork through missing versions, identifiers, hashes and licences until each release passes the CRA readiness checks.
  4. Monitor and recordTriage new vulnerabilities with VEX and keep the evidence with each release.
Common questions

Cyber Resilience Act: questions we hear

Does the CRA require an SBOM?

Yes. Annex I, Part II requires manufacturers to identify and document components, including an SBOM in a commonly used, machine-readable format covering at least top-level dependencies.

Do I have to publish my SBOM?

No. It belongs in your technical documentation and must be provided to market surveillance authorities on request. You can choose to share it with customers.

Does SBOMBox certify CRA compliance?

No. SBOMBox produces and organises evidence. Conformity assessment and legal interpretation remain with you, your counsel and, where required, a notified body.

Which SBOM format should I use?

The CRA does not mandate one. SBOMBox accepts CycloneDX and SPDX.

Book a demo

See it with your own SBOM.

A 30-minute walkthrough focused on Cyber Resilience Act. Bring a CycloneDX or SPDX file and we will score it live against BSI TR-03183-2, CISA, NTIA and CRA checks.