sbomify logo

CRA reporting obligations apply now Main obligations from 11 December 2027

Stay CRA ready for every release you support

The Cyber Resilience Act makes vulnerability handling a legal duty for as long as a product is supported. sbomify gives your team one place to know what you ship, decide on every vulnerability, report on time and prove it.

The timeline

The clock is running. Reporting applies today.

The CRA phases in over eighteen months. Two of its three dates have passed, and the last one makes every essential requirement enforceable.

  1. 11 June 2026 Applies Notified bodies Rules for conformity assessment bodies begin to apply.
  2. 11 September 2026 In force Article 14 reporting Report actively exploited vulnerabilities and severe incidents to ENISA within 24 hours.
  3. 11 December 2027 Upcoming Full application SBOMs, vulnerability handling and every essential requirement become enforceable.
to send an early warning once you know a vulnerability is actively exploited
24 hours
the usual minimum support period, with vulnerability handling throughout (Article 13(8))
5 years
or 2.5% of worldwide turnover, the ceiling for breaching Articles 13 and 14 (Article 64(2))
€15M
Article 14 reporting

24 hours to report. Start with the answer.

Once you know a vulnerability is actively exploited, the early warning is due within a day. Its first questions are inventory questions: which product, which versions, where. sbomify already knows.

  • Find every affected release in seconds, straight from the SBOMs pinned to each one.
  • Spot exploitation early. Known-exploited vulnerabilities from CISA KEV and EUVD are flagged as they appear.
  • Start from a draft. The early warning, the notification and the final report are drafted from the data you already hold.

You submit through the ENISA Single Reporting Platform; sbomify does not file for you.

CVE-2026-XXXXX Actively exploited

In Acme Router v2.0 and v2.1 · flagged by CISA KEV

  1. 24 h Early warningProduct, versions, Member States Draft ready
  2. 72 h NotificationAssessment and measures taken Draft ready
  3. 14 d Final reportOnce a fix is available After the fix
Illustrative example of the three Article 14 reports for one vulnerability.
Annex I, Part II

Vulnerability handling. Without the spreadsheets.

The CRA's vulnerability-handling requirements as one connected workflow, release after release, for every product you support.

An SBOM for every release

CycloneDX and SPDX from your pipelines, validated, checked against BSI TR-03183-2 and pinned to the release they describe.

Monitoring that never stops

Released SBOMs are rescanned with Google OSV and Dependency-Track for the whole support period, not just at build time.

Decisions on the record

Triage as VEX, track remediation and fix deadlines, and hand fix prompts to your coding agents. Every change keeps its history.

Disclosure your customers can use

Advisories in your Trust Center and as a CSAF 2.0 feed, with security.txt and the Transparency Exchange API for machines.

Annex I, Part II has eight requirements. sbomify builds in two, supports four and leaves two with you. See every obligation

CRA Compliance Wizard

Your technical file, drafted. From data you already hold.

The wizard turns your product profile, SBOMs and vulnerability records into the documents the CRA asks for, then exports them as one bundle ready for you to review and sign.

  • Policies and instructions, including a vulnerability disclosure policy, user instructions and a secure decommissioning guide.
  • A draft declaration of conformity. Signing it, and the CE marking, stay with you.
  • Evidence that holds up, with an OSCAL assessment and a SHA-256 manifest over every file.

On the Business and Enterprise plans. How the wizard works

CRA export bundleAcme Router v2.1
  • SBOMsCycloneDX, SPDX
  • OSCAL assessmentJSON
  • Vulnerability disclosure policyDraft
  • Cybersecurity risk assessmentTemplate
  • User instructionsDraft
  • Secure decommissioning guideDraft
  • EU declaration of conformityDraft
  • ManifestSHA-256

Ready for your review and signature

Coverage

What sbomify covers. And what stays yours.

No tool makes you CRA compliant on its own. Of sixteen manufacturer obligations, here is where sbomify stands.

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, like security testing and shipping updates

Read the guide: every CRA obligation, mapped

Questions

Before you start

Will sbomify make us CRA compliant?

No tool can. Compliance covers how you design, test and assess your product as well as how you handle vulnerabilities after release. sbomify runs the second half and drafts much of the paperwork; the obligations guide shows exactly where it fits.

Does sbomify submit Article 14 reports for us?

No. sbomify drafts the early warning, the notification and the final report, and you submit them through the ENISA Single Reporting Platform. Register your EU Login accounts and representatives there before you need them.

We already run a vulnerability scanner. Why sbomify?

Scanners find vulnerabilities. sbomify uses Google OSV and Dependency-Track to do that, and adds what the CRA asks for around them: SBOMs pinned to releases, support periods, VEX decisions with their history, and advisories your customers can read.

Can we run sbomify on our own infrastructure?

Yes. sbomify is open source and runs with Docker Compose. Read the self-hosting guide, or use our cloud at app.sbomify.com.

Which plan do we need?

The free Community plan covers SBOM management, OSV scanning with weekly rescans and a public Trust Center. Business and Enterprise add the CRA Compliance Wizard, daily rescans, Dependency-Track, private documents and a Trust Center on your own domain. See pricing.

Ready when you are

Get CRA ready, from SBOM to security disclosure

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