Enterprise

SBOM governance across every product and team

Large organisations rarely lack SBOMs. They lack one consistent way to produce, check and keep them across dozens of teams, products and suppliers. SBOMBox gives security and compliance teams a governed record for every release, while engineering keeps generating SBOMs in its own pipelines.

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.

Enforce policy in CI

Set a minimum quality score, licence allow and deny lists and required metadata. GitHub and GitLab integrations post the result as a commit status.

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.

Access control that matches your organisation

Sign in with SSO and provision users with SCIM on the Enterprise plan. Owner, admin, member, auditor and viewer roles keep auditors read-only, and MFA can be enforced for the whole organisation.

An audit trail you can prove

Sign-ins, token and permission changes, uploads and exports are written to an append-only, hash-chained audit log with CSV export and on-demand integrity checks.

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.

Getting started

How teams roll it out

  1. Start with a pilotConnect one or two products and agree the scoring profiles and policy that matter to you.
  2. Roll out through CIAdd the CLI or the GitHub and GitLab integrations to each team's pipeline. Policy results post back as commit statuses.
  3. Govern centrallySecurity and compliance teams monitor vulnerabilities, review VEX decisions and export evidence for auditors and customers.
Common questions

Enterprises: questions we hear

Do you support SSO and SCIM?

Yes, on the Enterprise plan, together with audit log export, custom retention and a custom domain.

Can auditors get read-only access?

Yes. The auditor and viewer roles can see results and evidence without changing projects or policy.

Do you sign a DPA and offer an SLA?

Yes. Enterprise agreements include a Data Processing Addendum, an SLA and dedicated support. Our subprocessors are listed publicly.

Do you see our source code?

No. Generation runs in your environment and only the SBOM and its provenance are uploaded.

How is Enterprise priced?

Enterprise pricing is custom. Book a demo and we will scope it around your products and requirements.

Book a demo

See it with your own SBOM.

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