Skip to main content
Bluecoders
← Tech glossary

SBOM

TermConcept

SBOM = the ingredient list of a piece of software

An SBOM (Software Bill of Materials) is a structured, machine-readable inventory of every component that makes up a piece of software: libraries, direct and indirect dependencies, versions, licenses and hashes.

In practice, it is generated automatically at build time and stored with each shipped release. When a vulnerability is disclosed in a widely used library, teams query their SBOMs to find out within minutes which products are affected, instead of combing through every repository by hand.

The two standard formats are SPDX (backed by the Linux Foundation) and CycloneDX (backed by OWASP). SBOMs have been required to sell software to the US federal government since Executive Order 14028, and the European Cyber Resilience Act requires manufacturers of digital products to document their components.

Why it matters when hiring

This falls to an AppSec Engineer, a Product Security Engineer or a DevSecOps profile. In interviews, ask how the SBOM is produced in CI, where it is stored and what happens the day a critical CVE drops: a real practitioner describes an end-to-end flow. Someone who only names the formats has read the documentation, not built the system.

A recruitment need?

Describe what you need. A recruiter from your sector will call you back within 24 business hours.