Version 2.0 · Last updated

Security

SBOMBox holds the evidence your customers and regulators rely on, so security is the product. This page lists the controls we operate today, without marketing claims. To report a vulnerability, email dpo@sbombox.com; our machine-readable contact details are in security.txt.

1. Customer-side execution

SBOMs are generated in your environment by the open-source CLI or our CI integrations. Only the resulting SBOM document and project metadata are uploaded. We never clone repositories and never receive source code, build artefacts or secrets. Generation, scoring and checks also work fully offline, and the CLI contains no telemetry.

Exactly what each tool sends is listed in section 6 of the Privacy Policy.

2. Identity and access

  • Passwordless sign-in with GitHub, GitLab, Google or an emailed one-time code. We hold no passwords to steal.
  • Optional authenticator-app MFA (TOTP) with hashed one-time recovery codes; TOTP secrets are encrypted at rest with a dedicated key.
  • Organisation owners can require MFA for every member; members without it are blocked with a clear remediation path.
  • Role-based access (owner, admin, member, auditor, viewer) enforced on every API request, with every query scoped to the caller’s organisation.
  • API tokens are scoped and stored only as a peppered HMAC hash; we cannot show a token again after it is created.
  • Short-lived OAuth access tokens with rotating refresh tokens and replay detection.
  • A session list with remote sign-out, and token revocation that takes effect immediately.

3. Keyless CI and provenance

Pipelines do not need a stored SBOMBox secret. In GitHub Actions or GitLab CI the CLI presents the provider’s signed OIDC identity token, which we verify against the trust rules your organisation set (repository, workflow, branch). We then issue a token that lasts 15 minutes and can only upload SBOMs to that one project.

The verified claims (repository, workflow, commit and run) are recorded on every SBOM uploaded this way, so you can prove where a piece of evidence came from. Only project administrators can change trust rules, and every change is recorded in the audit log with the before and after values.

4. Tamper-evident audit logging

Authentication, MFA, token, membership, CI trust, settings, privacy and data actions are written to an append-only log. Each entry includes the previous entry’s hash, so any alteration breaks the chain. Administrators can verify integrity on demand and export the log as CSV or JSON for auditors. Database triggers block updates and deletes. A logging failure never blocks a user, but it raises an alert.

5. Data protection

6. Application and web security

  • A strict Content Security Policy, frame-ancestors denial, nosniff, a strict referrer policy and a locked-down Permissions-Policy on every page.
  • Request throttling on the API and public forms.
  • Errors returned as structured problem documents that never include stack traces or internal details.
  • Error monitoring configured not to collect personal data by default.

7. Our own software supply chain

We hold ourselves to the standard we help you meet.

  • Every third-party GitHub Action in our pipelines is pinned to a full commit SHA, not a movable tag.
  • Automated dependency updates for Python, npm, Docker images and GitHub Actions.
  • Lockfile-frozen builds and tests on every change.
  • We generate and score an SBOM of SBOMBox itself in CI, using our own GitHub Action.
  • CLI releases are published with build-provenance attestations you can check with the GitHub CLI (gh attestation verify).
  • The installer downloads the CLI and SBOM generator from their official sources, verifies checksums and pins versions.

8. Operations and incident response

  • Least-privilege production access, granted only to people who need it, with access logged.
  • Confidentiality obligations and security training for anyone with access to customer data.
  • Managed database backups and documented recovery procedures.
  • Subprocessors are reviewed before we engage them and bound by equivalent security terms; we give 30 days’ notice of changes.
  • An incident response runbook: affected customers are notified within 48 hours of us confirming a personal data breach, and regulators within 72 hours where the law requires (see DPA section 10).

9. Vulnerability disclosure policy

Email dpo@sbombox.com with a description, steps to reproduce or a proof of concept, the affected component and version, and whether the issue is already public. For issues in our open-source code you can also use Report a vulnerability under the repository’s Security tab. Please do not open public issues for security bugs. We can provide a PGP key on request.

What we commit to

In scope

  • sbombox.com, the dashboard and the SBOMBox API.
  • The CLI, core library, installer, GitHub Action and GitLab component.
  • Authentication, MFA, token handling, CI trust and tenant isolation.
  • Storage integrity and the audit log.

Out of scope

  • Denial-of-service and volumetric testing, spam, and social engineering of our staff or customers.
  • Physical attacks, and issues in third-party services we do not control (report those to the vendor).
  • Missing best-practice headers or settings without a demonstrated impact, and reports produced only by automated scanners.
  • Vulnerabilities in open-source packages listed in a customer’s SBOM. Report those to the package maintainer.

Safe harbour

If you act in good faith and follow this policy, we will consider your research authorised, will not pursue or support legal action against you, and will work with you to understand and fix the issue. Good faith means: only test against accounts you own or have permission to use, do not access, change or keep other customers’ data beyond the minimum needed to show the issue, stop and tell us as soon as you reach personal data, do not degrade the Services, and give us reasonable time to fix the issue before disclosing it.

10. Acknowledgments

We thank everyone who reports issues responsibly. Researchers who report a confirmed vulnerability are listed here with their permission. No reports have been published yet; yours could be the first. Report to dpo@sbombox.com.

11. Compliance programme

We maintain a control matrix mapped to SOC 2 Trust Services Criteria, ISO/IEC 27001 Annex A, GDPR Articles 5, 15-22, 25, 30, 32 and 33, and PDPA obligations. We do not yet hold a SOC 2 report or ISO 27001 certificate, and we will say so plainly until we do.

For security questionnaires, our control documentation or a call with our team, email sia@sbombox.com. Our contractual commitments are in the Data Processing Addendum.

Privacy · Terms · DPA · Subprocessors · Privacy requests · Security