The Minimum Elements for a Software Bill of Materials (SBOM)¶
National Telecommunications and Information Administration. (2021). The Minimum Elements for a Software Bill of Materials (SBOM). U.S. Department of Commerce.
Cited by¶
2 citations across 2 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Complete Enumeration
- In software, a bill of materials and transitive dependency closure enable blast-radius analysis, which requires every transitive dependency, since a sampled dependency tree is useless for "who is downstream of this vulnerable library?"
This sourceSpecifies that an SBOM should enumerate components and their transitive dependencies (the full dependency closure), enabling blast-radius/vulnerability analysis that a sampled dependency tree cannot support. (Resolves needs-source-003 with a software-supply-chain-security reference.)
- In software, a bill of materials and transitive dependency closure enable blast-radius analysis, which requires every transitive dependency, since a sampled dependency tree is useless for "who is downstream of this vulnerable library?"
Mechanisms¶
- Machine-Readable Manifest
- The discipline that guards against this is to generate manifest fields from the build's source of truth and validate them in CI, treating a manifest-vs-reality mismatch as a build failure — the same instinct behind a software bill of materials, which is only useful if it is derived rather than asserted.
This sourceDefines an SBOM as a formal record of software components and their supply-chain relationships.
- The discipline that guards against this is to generate manifest fields from the build's source of truth and validate them in CI, treating a manifest-vs-reality mismatch as a build failure — the same instinct behind a software bill of materials, which is only useful if it is derived rather than asserted.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. Neither this nor any other of the 2 citations of this work carries a recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:4be966f4723a · see in the full table