sbomify logo

GuidesCyber Resilience Act

CRA obligations: what sbomify covers

The Cyber Resilience Act asks manufacturers to design secure products, assess their conformity, then handle vulnerabilities for as long as each product is supported. sbomify is built for that second half.

Built in
3
sbomify does this
Supports
9
sbomify gives you the data or a draft; you complete it
Yours
4
Outside sbomify's scope

sbomify will not make you CRA compliant on its own, and no tool can. Each obligation below says where sbomify fits in your own process.

Annex I, Part II

Vulnerability handling. The core of sbomify.

These requirements apply for the whole support period of a product, release after release. This is where sbomify does most of its work.

Part II (1) Built in

Identify and document components, including an SBOM

Generates CycloneDX and SPDX SBOMs in CI, validates them against the official schemas and checks them against BSI TR-03183-2. Component SBOMs are pinned to product releases and merged into one SBOM per release. Stored SBOMs are never modified.

Part II (2) Supports

Address and remediate vulnerabilities without delay

Rescans released SBOMs on a schedule with Google OSV and Dependency-Track, flags CISA KEV and EUVD entries, and shows which products and releases contain each vulnerability. Triage decisions are recorded as VEX, remediation status and fix deadlines are tracked, and fix prompts can be handed to your coding agents. Writing and shipping the fix is your work.

Part II (3) Yours

Regular security tests and reviews

Penetration tests, code review and security testing happen outside sbomify. You can store the resulting reports alongside your SBOMs and share them through your Trust Center.

Part II (4) Built in

Publicly disclose fixed vulnerabilities

Write security advisories that list affected products and releases, severity and remediation, then publish them in your Trust Center and as a CSAF 2.0 feed with provider-metadata.json and a ROLIE feed. Every change to an advisory is kept on its timeline.

Part II (5) Supports

Coordinated vulnerability disclosure policy

The CRA Compliance Wizard drafts a vulnerability disclosure policy from your product details. Running the process it describes is up to you.

Part II (6) Supports

Contact address for reporting vulnerabilities

Generates a security.txt file pointing researchers to your contact address, policy and advisories. You own the inbox and the response.

Part II (7) Yours

Securely distribute updates

Signing and delivering software updates is part of your release infrastructure, not sbomify.

Part II (8) Supports

Disseminate security updates with advisory messages

sbomify publishes the advisory that goes with each update, to people through the Trust Center and to machines through CSAF and the Transparency Exchange API. Shipping the update itself is yours.

Articles 13 to 32

Everything else. sbomify drafts, you sign.

Other manufacturer obligations, around the product as a whole. sbomify supplies data and drafts for several of them; the decisions and signatures are yours.

Article 13(8) Built in

Support period

Records release, end-of-support and end-of-life dates for products, components and releases using the ECMA-428 Common Lifecycle Enumeration, and helps you publish an end-of-life notice when support ends. Choosing the support period is your decision.

Article 14 Supports

Reporting actively exploited vulnerabilities and severe incidents

Drafts the 24-hour early warning, the 72-hour notification and the final report from the data you already hold, and flags known-exploited vulnerabilities. sbomify does not submit reports for you: they go through the ENISA Single Reporting Platform.

Article 31, Annex VII Supports

Technical documentation

The CRA Compliance Wizard exports one bundle with your SBOMs, an OSCAL assessment, the generated documents and a SHA-256 manifest, ready for you to sign. The parts about product design and testing come from you.

Article 13(2) Supports

Cybersecurity risk assessment

Provides a risk assessment template as part of the wizard. The assessment itself has to reflect your product and your threat model.

Annex II Supports

Information and instructions for users

Drafts user instructions and a secure decommissioning guide, and lets you share them, along with the SBOM, through your Trust Center.

Articles 28 to 30 Supports

EU declaration of conformity and CE marking

Drafts the declaration of conformity from your product profile. Signing it, and affixing the CE marking, is a legal act by the manufacturer.

Annex I, Part I Yours

Essential cybersecurity requirements for the product

Secure by design and by default, access control, data protection, attack surface reduction and logging are properties of your product. sbomify doesn't build or test them.

Article 32 Yours

Conformity assessment

Self-assessment or assessment by a notified body, depending on your product's class. sbomify's export bundle is evidence for that process, not a substitute for it.

Plan availability

Start free. Add the wizard when you need it.

SBOMs, scanning and a public Trust Center cost nothing. The CRA Compliance Wizard comes with Business and Enterprise.

CommunityFree

  • SBOM management
  • OSV scanning, rescanned weekly
  • A public Trust Center

Business and EnterpriseEverything in Community, plus

  • The CRA Compliance Wizard, its generated documents and the export bundle
  • Daily rescans and Dependency-Track
  • Private documents
  • A Trust Center on your own domain

See pricing for the details, or sbomify for the CRA for the product. For the legal text behind each obligation, deadlines and penalties, read our EU CRA guide

Ready when you are

Start handling CRA vulnerabilities in one place

Know what is in every release, decide on each vulnerability and tell your customers, from one platform you can run in our cloud or your own.

  • Free to start
  • Open source
  • Cloud or self-hosted