The jargon, in plain English.
Software security is full of acronyms. Here is what each one means, in a sentence or two. New to the topic? Start with SBOMs explained.
- AI-BOMAI bill of materials
An SBOM extended to cover an AI system's models, datasets and AI services as well as its software. CycloneDX calls it an ML-BOM.
Learn more- Attestation
A signed statement about how something was built, for example “this SBOM was produced by this build, from this commit”. Anyone can check the signature later.
Learn more- BSI TR-03183-2
A technical guideline from Germany's Federal Office for Information Security (BSI) that sets out, in detail, what a good SBOM must contain. Widely used as a reference for the CRA.
Learn more- CBOMCryptographic bill of materials
An inventory of the cryptography in software: algorithms, keys, certificates and protocols. It is the first step in moving to post-quantum cryptography.
Learn more- CI/CDContinuous integration and delivery
The automated system that builds, tests and releases software every time a developer makes a change. GitHub Actions and GitLab CI are common examples.
Learn more- CISACybersecurity and Infrastructure Security Agency
The US government agency for cybersecurity. It publishes the minimum elements an SBOM should contain (updated in 2026) and the list of vulnerabilities known to be exploited (KEV).
Learn more- Component
One building block inside a piece of software, such as an open-source library or package. Also called a dependency. An SBOM is a list of components.
- CRAEU Cyber Resilience Act
An EU law that requires products with software in them to be secure when sold and kept secure with updates. It requires an SBOM and the reporting of actively exploited vulnerabilities.
Learn more- CSAFCommon Security Advisory Framework
A standard, machine-readable format for security advisories: the notices vendors publish to tell customers about a flaw and how to fix it.
Learn more- CVECommon Vulnerabilities and Exposures
A public catalogue of known security flaws. Each flaw gets an ID such as CVE-2021-44228, so everyone can refer to the same problem.
- CycloneDX
One of the two standard SBOM file formats, maintained by the OWASP Foundation. Popular with security teams.
Learn more- Dependency
A component your software relies on. A direct dependency is one you chose; a transitive dependency is one that your dependencies pulled in.
- ENISAEU Agency for Cybersecurity
The EU agency that runs the single platform where companies report exploited vulnerabilities and serious incidents under the CRA.
Learn more- EPSSExploit Prediction Scoring System
A daily score that estimates how likely a known vulnerability is to be exploited in the next 30 days. It helps you decide what to fix first.
Learn more- KEVKnown Exploited Vulnerabilities
A list kept by CISA of vulnerabilities that attackers are already using in the real world. If a component is on it, fix it first.
Learn more- NIS2
An EU directive that raises cybersecurity duties for essential and important organisations, including managing risk in their software suppliers.
Learn more- NTIA minimum elements
The original 2021 US definition of the fields every SBOM should have, such as supplier, component name, version and a unique identifier. Replaced in 2026 by CISA's longer list of 17 fields.
Learn more- OIDCOpenID Connect
A way for a build system to prove who it is without storing a password or secret key. SBOMBox uses it so your CI can upload SBOMs securely.
- Open source
Software whose code is published for anyone to use, usually free of charge. Most modern products are largely built from open-source components.
Learn more- Provenance
Where something came from and who stands behind it. For an SBOM, this means who supplied each component and proof of how the SBOM itself was made.
Learn more- SBOMSoftware bill of materials
A machine-readable list of every component in a piece of software, with names, versions and suppliers. Think of it as an ingredients label.
Learn more- SPDX
One of the two standard SBOM file formats, maintained by the Linux Foundation and published as an international standard (ISO/IEC 5962). Strong on licence information.
Learn more- Support period
How long you promise to keep fixing security problems in a product. The CRA expects at least five years for most products.
Learn more- Technical documentation
The file of evidence a manufacturer must keep to show a product meets the CRA. The SBOM is one part of it.
Learn more- Trust center
A page where a company shares security documents, such as SBOMs and compliance results, with customers in one place instead of by email.
- VEXVulnerability Exploitability eXchange
A short statement that says whether a known vulnerability actually affects your product, and why. It stops customers chasing flaws that cannot be reached.
Learn more- Vulnerability
A flaw in software that an attacker could use to cause harm. Once it is public, it usually gets a CVE ID.