SBOM management for CRA compliance

The easiest way to generate and manage SBOMs.

An SBOM is the ingredients list for your software. Create one with a single command or in your build, check it against the EU Cyber Resilience Act and other rules, and keep signed proof for every release. Your source code never leaves your environment.

No source code uploadCycloneDX & SPDX3 projects free
Nothing is stored
CycloneDX 1.4-1.7SPDX 2.2-3.0
9compliance profiles
Dailychecks for new security flaws
24hCRA reporting clock tracked
0source code stored
New to SBOMs?

An ingredients list for your software.

Most software is assembled from hundreds of open-source pieces written by other people. An SBOM (software bill of materials) lists every one of them, with its version and who made it.

When a serious security flaw turns up in one of those pieces, the list tells you in minutes whether you are affected. That is why the EU, the US government and large customers now ask for one. SBOMBox creates these lists, checks them against the rules and keeps watching them for new problems.

The problem

Having an SBOM is not the same as being ready.

The EU Cyber Resilience Act, US government buyers and large customers now ask for SBOMs, a plan for fixing security flaws, and proof. Most teams can make the file. Few can show it is complete, up to date and trustworthy.

01

SBOMs are generated, then forgotten

A file saved somewhere in the build tells nobody whether it is complete, whether suppliers are named or whether it can be trusted.

02

Every regulator reads them differently

Germany’s BSI, the US agencies CISA and NTIA, and the EU’s CRA each define a “complete” SBOM in a different way.

03

Vulnerabilities outrun release cycles

A new security flaw can turn up in a release you have already shipped. If attackers are using it, the CRA gives you 24 hours to warn the authorities.

04

Evidence lives in spreadsheets

When an auditor or customer asks “prove it”, teams rebuild the story from CI logs and chat threads.

The solution

One evidence chain from commit to audit.

SBOMBox creates SBOMs where your code lives, checks them against published rules, watches them for new security flaws and keeps signed proof for every release.

Without SBOMBox

  • SBOMs sit in build artifacts, unchecked
  • Each regulator’s rules read by hand
  • New CVEs found by accident
  • Audit evidence rebuilt from CI logs

With SBOMBox

  • Generate: Generate locally. Source never leaves.
  • Audit: Requirement-level results, not a black-box score.
  • Monitor: Know the day a release becomes vulnerable.
  • Prove: Hand auditors a verifiable trail.
How we solve it

See the product, with example data.

These are the real SBOMBox screens rendered with sample data. Nothing here is a screenshot, and nothing is sent anywhere.

01 · Score & findings

Requirement-level results, not a black-box score.

Every field is checked against BSI, CISA, NTIA and CRA profiles. Each finding names the rule, the affected components and the fix.

  • 9 compliance profiles
  • Automatic and manual fix guidance
  • Score history per release
8.7/10 · A
Overall SBOM quality

Strong foundation. Four checks need attention.

Core identity and dependency data conforms to the rules checked. Supplier and support-period metadata remain incomplete.

1,248 components7 ecosystems98% with hashes
Estimated after fixes9.4 / 10 · A
BSI TR-03183-2v2.1
8.8 Apass
41 pass · 3 partial · 1 fail
CISA2025
7.6 Bpartial
15 pass · 4 partial · 1 fail
NTIA2021
9.2 Apass
7 pass · 1 partial · 0 fail
CRA readiness2027
6.9 Cpartial
19 pass · 5 partial · 2 fail
Requirement results

Findings

RequirementProfileAffectedResolutionStatus
BSI-SUP-01Supplier name is missingBSI TR-03183-2 v2.137automaticfail
CISA-HASH-02Cryptographic hashes are incompleteCISA 202512automaticpartial
NTIA-DEP-01Dependency relationship is not declaredNTIA8manualpartial
CRA-SUP-03Support period is not documentedCRA readiness1manualfail
Inventory preview

Components

ComponentVersionLicenseSupplierVulns
@fastify/corspkg:npm/%40fastify/cors@9.0.19.0.1MITFastify-
jsonwebtokenpkg:npm/jsonwebtoken@9.0.29.0.2MITAuth01
lodashpkg:npm/lodash@4.17.214.17.21MITOpenJS-
postgrespkg:npm/postgres@3.4.53.4.5Unlicenseunknown-
02 · Vulnerabilities

Know the day a release becomes vulnerable.

Every day your SBOMs are matched against newly published security flaws, with the ones attackers are already using (KEV) and the ones most likely to be used next (EPSS) at the top. CRA 24-hour and 72-hour reporting clocks start the moment you confirm an issue.

  • KEV and EPSS prioritisation
  • VEX decisions kept with the release
  • Deadline tracking for CRA notifications
AdvisoryPackageFixSeverityProjectStatus
CVE-2026-31142KEVjsonwebtoken@9.0.29.0.3criticalEdge Agentopen
CVE-2026-20881KEVopenssl@3.0.113.0.14criticalDevice Firmwareopen
CVE-2026-19204busybox@1.36.01.36.1highDevice Firmwarein-progress
CVE-2026-15337fastify@4.26.04.27.0highCheckout APIopen
CVE-2025-49812lodash@4.17.204.17.21mediumAdmin Consoleresolved

CRA reporting clocks

  • Early warning: actively exploited vulnerabilityEdge Agent · 24h early warning
    in 3 hoursfail
  • Incident report: firmware update channel outageDevice Firmware · 72h incident notification
    in 2 dayspartial
  • Annex I security requirements self-assessmentCheckout API · Conformity evidence
    in 11 dayspartial
  • Support period statement publishedAdmin Console · Documentation
    donepass
03 · Audit log

Hand auditors a verifiable trail.

Signed provenance, a tamper-evident audit log and shareable reports let customers and assessors verify instead of trust.

  • P3 signed provenance
  • Hash-chained audit log with verification
  • Public report links and trust center
Audit logEvery action, who did it, from where
Chain verified · 1,284 entries
mfaEnabled authenticator apppriya@acme.io · 203.0.113.24mfa.totp.enabledsuccess9f3a…c21e
authSigned inpriya@acme.io · 203.0.113.24auth.loginsuccess41be…07da
authFailed sign-in attemptunknown · 198.51.100.9auth.login_failedfailedb7c0…92f4
api_keyOIDC token for checkout-apici@checkout-api · 192.0.2.77token.issuedsuccess02d8…5aa1
projectUploaded SBOM v2.14.0marco@acme.io · 203.0.113.58project.sbom.uploadsuccesse4a1…3b60
orgMarco → adminpriya@acme.io · 203.0.113.24org.member.role_changedsuccess7c55…d0e8
privacyExported personal datapriya@acme.io · 203.0.113.24export.personal_datasuccessa9f2…18c7
04 · Security & MFA

Sign-in you can defend to an auditor.

Add an authenticator app in a minute, keep recovery codes safe, and let organisations require MFA for every member.

  • TOTP with recovery codes
  • Email one-time codes for step-up
  • Org-wide “require MFA” policy
Authenticator appTime-based one-time codes (TOTP)
Enabled
482913
Works with 1Password, Authy, Google Authenticator
Recovery & email codesNever locked out
4820193770314856159274039206817433851609
Email a one-time code to step up or disable MFA. Organisations can require MFA for every member.
05 · Your data

Privacy rights, self-serve.

Export what we hold about you, close your account with a grace period, or file a request that is tracked to its 30-day deadline.

  • Personal data export
  • DSAR tracking with SLA
  • Versioned consent records
Your dataRights under GDPR, UK GDPR, PDPA, DPDP & CCPA
  • Download a copy of your personal data (JSON)
  • Delete your account - 14-day grace period
  • Cookie & consent choices, versioned
Privacy requestsAnswered within 30 days
  • Access my dataDSAR-1042
    in 21 daysIn progress
  • Delete my dataDSAR-1038
    closedCompleted
One evidence chain

Every release tells a complete story.

Generate at the source, measure against published requirements, and keep evidence linked to the exact release.

01

Generate

Run locally or in CI. Your source stays where it belongs.

02

Audit

Check every field against BSI, CISA, NTIA and CRA profiles.

03

Monitor

Track vulnerability and compliance drift across releases.

04

Prove

Share signed, verifiable evidence with customers and auditors.

Built for real release pipelines

From commit to CRA evidence.

SBOMBox keeps each release's SBOM, compliance results, vulnerability decisions and support dates together, without adding another scanner to your pipeline.

  • Signed in CI with no stored secrets
  • A clear list of what passes and fails, not a black-box score
  • Signed history for every release
Set up the GitHub Action
release.yml
name: Generate signed SBOM

uses: sbombox/action@v1
with:
 project: checkout-api
 attest: true
checkout-api · v2.14.0Build signature verified · Score 8.7 / 10
Solutions

Built for the rules you answer to.

Whether the question comes from the CRA, NIS2, the FDA, a PCI assessor or a customer questionnaire, and whether you are a startup or a global enterprise, start from the guide written for you.

Frequently asked questions

SBOMs and the CRA, answered.

What is an SBOM?

A Software Bill of Materials (SBOM) is an ingredients list for software. It is a machine-readable file that names every component, library and version inside a product, so you can tell at once whether a newly found security flaw affects you. CycloneDX and SPDX are the two standard formats.

Do I need an SBOM for the EU Cyber Resilience Act (CRA)?

Yes, if you sell software or connected devices in the EU. The CRA requires a machine-readable SBOM that lists at least your direct dependencies. The SBOM rule applies from 11 December 2027. Reporting exploited vulnerabilities has been required since 11 September 2026.

How do I generate an SBOM?

Install the SBOMBox CLI with one command and run it in your repository, or add the SBOMBox GitHub Action to generate a signed SBOM on every release. GitLab CI is also supported.

Does SBOMBox see my source code?

No. SBOMs are generated locally or in your CI. SBOMBox receives only the finished SBOM, never your source code.

How do I check if my SBOM is complete and valid?

Drop a CycloneDX or SPDX file into the free checker on this page. In seconds you get a quality score across 8 categories, showing what passes and what to fix. Nothing is stored.

Which SBOM formats are supported?

CycloneDX 1.4 to 1.7 and SPDX 2.2 to 3.0, in JSON or XML.

How does SBOMBox help with CRA vulnerability reporting?

SBOMBox checks your SBOMs for new vulnerabilities, including ones attackers are already exploiting. If one affects you, log it as a CRA incident. Its reporting deadlines stay next to the affected release.

How do I share SBOMs with customers?

Publish selected SBOMs and compliance results to your SBOMBox Trust Center and share them privately with customers, instead of emailing files.

How much does SBOMBox cost?

Three projects are free. After that it is $29 per project per month, with no per-seat or per-scan fees.

Start with one project, free

Make your next SBOM worth trusting.