Makes the list
One command, or one step in your build, creates the SBOM on your own machines. Your source code is never sent to us.
A five-minute introduction for anyone who is curious: what an SBOM is, why governments and customers are asking for one, and what SBOMBox does about it.
An SBOM, or software bill of materials, is an ingredients list for software.
Almost no app is written from scratch. A typical product is built from hundreds of ready-made pieces: open-source libraries, frameworks and packages written by other people. An SBOM lists every one of those pieces, with its name, its version and who made it.
It is a file that computers can read, so tools can check it automatically. Nobody writes one by hand. A tool scans the software and produces it in seconds.
Every so often a serious security flaw is found in a popular building block. In December 2021 it was Log4j, a small logging library used inside millions of products. Attackers started using the flaw within hours.
Companies with an up-to-date list of their ingredients could answer “are we affected?” in minutes. Everyone else spent days or weeks searching through their software by hand, while staying exposed.
That is the whole point of an SBOM: when the next problem appears, you already know where to look.
After incidents like Log4j, regulators decided that knowing what is inside your software should not be optional.
In the European Union, the Cyber Resilience Act (CRA) will require anyone selling software or connected devices in the EU to keep an SBOM from 11 December 2027. The US government asks its software suppliers for SBOMs, and the FDA requires them for many medical devices.
Large companies are doing the same thing in their buying process. If you sell software to a bank, a hospital or a government, expect to be asked for an SBOM.
Free tools can produce an SBOM in seconds. The hard part comes after.
Is the list complete? Does it contain the details a regulator expects, such as who supplies each piece? Is it still accurate after this week's release? Has a new security flaw been found in something on the list since yesterday? And can you prove all of this to a customer or an auditor?
Most teams answer those questions with spreadsheets, scripts and a lot of manual work.
SBOMBox is a service for software teams. It creates SBOMs, checks them against the rules, keeps watching them for new security flaws, and keeps the proof.
One command, or one step in your build, creates the SBOM on your own machines. Your source code is never sent to us.
We compare the SBOM with the rules in the CRA and the US and German government guidelines, and tell you exactly what is missing and how to fix it.
Every day we check your ingredients against newly published security flaws, and flag the ones attackers are already using.
Each release keeps a signed, tamper-evident record, so you can show customers and auditors the evidence instead of asking them to trust you.
No. Any team that ships software benefits from knowing what is inside it. Tools make an SBOM for free in seconds, and small teams are often the ones asked for one by larger customers.
No. An SBOM lists the third-party pieces you use and their versions. It does not contain your own code.
No. An SBOM is the list of ingredients. A vulnerability scan compares that list with known security flaws. The SBOM stays useful long after the scan, because you can re-check it whenever a new flaw is published.
Every time you release a new version. The easiest way is to generate it automatically as part of your build.
Met an acronym you do not know? See the glossary.