sbom.wiki

District 01 SBOM-DEF

What is SBOM

A Software Bill of Materials is a comprehensive inventory of all components, libraries, and modules that comprise a software application. Like a city's infrastructure registry that catalogs every pipe, cable, and structural beam beneath the streets, an SBOM maps the invisible architecture that holds modern software together.

In an era where a single application may contain thousands of open-source dependencies, the SBOM serves as the definitive record -- the municipal ledger that tracks provenance, versioning, and licensing across the entire supply chain.

Format: SPDX | CycloneDX | SWID Mandate: EO 14028 (May 2021) Scope: All federal software procurement
EST. 2021
District 02 COMP-REG

Component Registry

Every software component carries an identity -- a name, a version, a provenance trail. The Component Registry is the census bureau of the software city, maintaining detailed records of every resident package, from core frameworks to the smallest utility library.

openssl v3.1.4 Apache-2.0 Validated
log4j-core v2.17.1 Apache-2.0 Review
lodash v4.17.21 MIT Validated
3 PACKAGES
District 03 DEP-GRAPH

Dependency Mapping

Dependencies form the hidden transit network of software -- invisible routes connecting components across organizational boundaries. A single application may traverse hundreds of dependency paths, each one a potential vector for supply chain compromise.

Mapping these relationships transforms the opaque tangle of node_modules and vendor/ directories into a navigable transit diagram where every connection is visible, every transfer point is monitored.

react@18.2.0
loose-envify@1.4.0
scheduler@0.23.0
DEPTH: 7
District 04 VULN-MON

Vulnerability Monitoring

When a vulnerability is discovered in any component, the SBOM becomes the emergency response map -- instantly identifying every application, every deployment, every environment where the compromised component resides. Without this map, organizations are searching for a broken pipe in a city with no blueprints.

CVE-2021-44228 Log4Shell CRITICAL 10.0
CVE-2023-44487 HTTP/2 Rapid Reset HIGH 7.5
CVE-2024-3094 XZ Utils Backdoor HIGH 8.6
3 ALERTS
District 05 STD-SPEC

Standards & Formats

The SBOM ecosystem converges around three principal formats, each serving as a dialect in the universal language of software transparency. Like transit systems that must interoperate across city boundaries, these standards enable machine-readable exchange of component data across organizational lines.

SPDX

Linux Foundation

ISO/IEC 5962:2021. The international standard for communicating software bill of materials information, including provenance, licensing, and security references.

CycloneDX

OWASP Foundation

A lightweight SBOM standard designed for use in application security contexts and supply chain component analysis.

SWID

ISO/IEC 19770-2

Software Identification tags providing authoritative identification of installed software for asset management and compliance.

3 FORMATS
District 06 CHAIN-SEC

Supply Chain Security

The software supply chain is the critical infrastructure of the digital economy. Every package registry, every build pipeline, every deployment mechanism is a link in a chain that stretches from individual developer workstations to production systems serving millions. The SBOM is the map of this chain -- the document that makes the invisible visible.

From executive orders mandating transparency to industry frameworks like SLSA and Sigstore, the movement toward comprehensive supply chain security is not a trend -- it is a permanent shift in how software is built, distributed, and trusted.

01 Source
02 Build
03 Package
04 Deploy
05 Monitor
5 STAGES