Frequently Asked Questions
Common questions about SBOMs, software supply chain security, and the sbomify platform. Get answers about SBOM formats, compliance requirements, and getting started.
No questions match your search.
What is an SBOM (Software Bill of Materials)?
An SBOM (Software Bill of Materials) is a machine-readable inventory of all components, libraries, and dependencies that make up a piece of software - like an ingredients list for your code.
Read full answerWhy do I need an SBOM?
You need an SBOM to track what's inside your software, respond quickly to vulnerabilities, meet regulatory requirements like the EU CRA, and build trust with customers and partners.
Read full answerWhat SBOM formats does sbomify support?
sbomify supports both CycloneDX and SPDX - the two industry-standard SBOM formats. CycloneDX 1.3 through 1.7 and SPDX 2.2, 2.3, and 3.0.1 are accepted in JSON representation, with automatic validation against official schemas. Beyond SBOMs, sbomify also accepts VEX documents (CycloneDX VEX, OpenVEX, CSAF 2.0) and CBOMs.
Read full answerCan I convert between CycloneDX and SPDX?
Not reliably. CycloneDX and SPDX have different data models, so converting between them inevitably loses context. The best approach is to generate natively in the format you need.
Read full answerCan I combine multiple SBOMs into one?
You can technically merge SBOMs, but it should generally be avoided because you lose the ability to tell where a particular component comes from. Use sbomify's hierarchy to link multiple SBOMs together instead.
Read full answerIs sbomify free?
Yes - sbomify offers a free Community tier for open-source maintainers and hobby projects. Paid Business and Enterprise plans are available for teams that need private SBOMs and advanced features.
Read full answerWhat is the EU Cyber Resilience Act (CRA)?
The EU Cyber Resilience Act (CRA) is a binding EU regulation requiring manufacturers of products with digital elements to provide SBOMs, handle vulnerabilities, and meet cybersecurity requirements throughout the product lifecycle.
Read full answerAre SBOMs required for Secure by Design?
Yes. SBOMs are a foundational requirement of Secure by Design. CISA, the EU Cyber Resilience Act, and US Executive Orders all mandate or strongly recommend SBOMs as essential to building and verifying secure software.
Read full answerHow do I sign an SBOM?
You sign an SBOM by wrapping it in a cryptographic attestation - typically using GitHub's built-in attestation support or Sigstore's cosign - so that anyone who receives the SBOM can verify it came from your CI/CD pipeline and was not tampered with in transit.
Read full answerHow do I use CRA compliance in sbomify?
Open a Product, run the CRA scope screening to confirm the product is in CRA scope, then walk through the five-step wizard (Product Profile, SBOM Compliance, Security & Vulnerability, User Information, Review & Export). Export produces a single self-contained ZIP with your SBOMs, OSCAL assessment results, generated documents, and a SHA-256 manifest, sign that ZIP with cosign on your side and you have a CRA compliance package ready for an auditor.
Read full answerHow do I generate an SBOM?
The easiest way is with sbomify-action, which generates, enriches, and uploads SBOMs from your lockfiles or Docker images in CI/CD. Run its interactive setup wizard (sbomify-action wizard) to get a working pipeline in minutes. You can also use standalone tools like Syft or cdxgen.
Read full answerHow do I use the sbomify setup wizard?
Run 'sbomify-action wizard' from the root of your repository using the Docker image, which bundles everything the wizard needs. The interactive wizard scans your repo for lockfiles, signs you in to sbomify, lets you pick or create the product and components, registers OIDC trusted publishing, and writes a ready-to-commit .github/workflows/sboms.yml. Commit the file and your next push generates and uploads an SBOM.
Read full answerHow do I set up OIDC trusted publishing?
Add a trusted publisher binding to your component in the sbomify app (Component Settings, Trusted Publishers), then grant your GitHub Actions workflow 'permissions: id-token: write' and drop the TOKEN secret. sbomify-action detects the OIDC environment automatically, exchanges GitHub's OIDC token for a short-lived sbomify token, and uploads. No secrets to create, rotate, or leak.
Read full answerHow do I enable vulnerability scanning in sbomify?
Enable the OSV plugin from the Plugins page in your workspace sidebar. It is available on all plans. Once enabled, SBOMs are scanned automatically on upload and periodically re-scanned. Dependency Track is available on Business and Enterprise plans.
Read full answerWhat VEX formats does sbomify support?
sbomify ingests VEX in three formats: CycloneDX VEX (JSON and XML), OpenVEX (the format used by vexctl and Chainguard), and CSAF 2.0 VEX (the OASIS standard used by vendors like Red Hat and Cisco). The format is detected automatically on upload, and statements are applied to your OSV and Dependency Track findings.
Read full answerHow do I use VEX with sbomify?
A VEX document tells consumers which vulnerabilities in your SBOM are actually exploitable in your product and which are not. sbomify ingests CycloneDX VEX, OpenVEX, and CSAF 2.0 VEX, applies your statements to OSV and Dependency Track findings so noise is suppressed, and publishes the VEX alongside your SBOMs in your Trust Center. You can also triage vulnerabilities directly in sbomify, generate a VEX from your decisions, and have sbomify flag statements that have gone stale or High and Critical findings that no statement covers.
Read full answerWhat is a CBOM and how does sbomify support it?
A CBOM (Cryptography Bill of Materials) is a CycloneDX BOM that inventories cryptographic assets: algorithms, keys, certificates, and protocols. sbomify auto-detects CBOM content on upload, renders a crypto-asset inventory, runs a post-quantum cryptography (PQC) readiness assessment against NIST guidance, and publishes CBOMs on your public release pages next to your SBOMs.
Read full answerHow does sbomify count vulnerabilities?
Vulnerability counts in sbomify reflect your current posture: the findings present in the latest artifact for each component and format, with VEX-suppressed findings excluded. They are not a running total across every historical SBOM version. If your counts dropped noticeably after upgrading to v26.7.1, that is the fix for exactly this behaviour landing - the earlier numbers were inflated by superseded SBOM versions.
Read full answerWhat is a Trust Center?
A Trust Center is a public-facing page where organizations share security artifacts like SBOMs, compliance documents, security advisories, and attestations with customers and partners - building transparency and trust.
Read full answerHow do I set up a Trust Center in sbomify? Business+
Go to Settings > Trust Center, enable it, optionally turn on security.txt and upload a Company NDA, then set your custom domain. Mark each component as Public, Gated, or Private to control what visitors can see. Trust Center requires a Business plan or higher.
Read full answerHow do I enable the Transparency Exchange API (TEA) in sbomify? Business+
Enable your Trust Center under Settings > Trust Center, configure and validate a custom domain, then toggle on TEA. TEA requires a Business plan or higher.
Read full answerWhat is a security advisory?
A security advisory is a vendor's public notice about a vulnerability in its own product: what is affected, how severe it is, which versions are fixed, and what customers should do. A good advisory names the CVE, gives a CVSS score and vector, lists affected and fixed version ranges per product, and keeps a dated timeline. Publishing one in a machine-readable format such as CSAF 2.0 lets customers' tooling consume it automatically.
Read full answerWhat is a PSIRT?
A PSIRT (Product Security Incident Response Team) is the function inside a vendor that receives, triages, fixes and discloses vulnerabilities in the products the company sells. Unlike a CSIRT, which protects the company's own infrastructure, a PSIRT protects customers by publishing security advisories, coordinating with researchers and issuing fixes.
Read full answerHow do products work in sbomify?
sbomify organizes SBOMs using a hierarchy: components hold individual SBOMs (usually one per repository), products group related components and represent what you sell or distribute, and releases version your products.
Read full answerHow do I upload compliance documents?
Compliance documents live on Document-type components. From Components, create a workspace-wide Document component (e.g. SOC 2 Type II Compliance), then upload the file with its version, document type, subcategory, and description.
Read full answerHow do I create a software release in sbomify?
Upload your component SBOMs first, then create a product release that points to specific SBOMs. Each SBOM can have its own version and be shared across multiple releases.
Read full answerWhat is a vulnerability disclosure program?
A vulnerability disclosure program (VDP) is the published process by which an organisation accepts security vulnerability reports from outside researchers, handles them, and discloses them in coordination with the reporter. Its core is a vulnerability disclosure policy that says what is in scope, how to report, what the reporter can expect, and a safe-harbour commitment not to pursue good-faith research.
Read full answerWhat is security.txt?
security.txt is a plain-text file, defined in RFC 9116, served at /.well-known/security.txt. It tells security researchers how to report a vulnerability to you. Contact and Expires are required; optional fields include Policy, Encryption, Acknowledgments, Preferred-Languages, Canonical, Hiring, and CSAF, which points to your CSAF advisory feed.
Read full answerHow do I delete a workspace?
You can delete a workspace from the workspace settings page. This permanently removes the workspace and all its data, including components, SBOMs, and documents.
Read full answerHow do I delete my account?
Open Settings > Account, expand the Danger Zone, click Delete Account, type 'delete' to confirm, then click Delete My Account. This permanently removes your account and all associated data.
Read full answerHow do I become a CVE Numbering Authority (CNA)?
A CVE Numbering Authority (CNA) is an organisation authorised by the CVE Program to assign CVE IDs and publish CVE records for vulnerabilities within an agreed scope, usually its own products. To become one, you need a public vulnerability disclosure policy, a public place where you publish advisories, and agreement to follow the CNA rules. You then contact the CVE Program or a Root CNA, define your scope, and complete onboarding. There is no fee.
Read full answerHow do I achieve NTIA/CISA minimum elements compliance?
Use sbomify-action's augmentation feature to automatically add required metadata like supplier info, authors, licenses, and lifecycle phase to your SBOMs - either via a local config file or centrally managed profiles in sbomify.
Read full answerHow do I attach signatures and provenance to SBOMs?
sbomify accepts a detached signature on every SBOM via `POST /api/v1/sboms/sbom/<id>/signature` (with an `X-Signature-Type` header naming `cosign-bundle`, `pgp-detached`, or `pkcs7`) and a separate in-toto / DSSE provenance attestation via `POST /api/v1/sboms/sbom/<id>/provenance`. Once attached, Signed and Provenance badges appear on the SBOM detail page and the SBOM Verification plugin runs five checks (digest integrity, signature presence + validity, provenance presence + digest match) on every assessment cycle.
Read full answerStill have questions?
Book a demo and we'll answer them on a call, using your own products. Or start free and try it yourself.