Software Bill of Materials (SBOM) - FOSSA

Software Bill of Materials (SBOM)

A formal, machine-readable inventory that lists all components and dependencies included in a software application, providing transparency into the software supply chain.

What is a Software Bill of Materials (SBOM)?

A Software Bill of Materials (SBOM) is a formal, machine-readable inventory that identifies and lists all software components, libraries, modules, and dependencies included in an application. Similar to how a list of ingredients appears on food packaging or a bill of materials is used in manufacturing, an SBOM provides transparency and visibility into the composition of software products.

SBOMs have emerged as a critical tool for software supply chain security, vulnerability management, license compliance, and overall risk reduction. They enable organizations to understand what's in their software, track vulnerable components, and respond quickly to newly discovered security issues.

Core Components of an SBOM

Component Identification

Component Metadata

Dependency Relationships

Vulnerability Information

SBOM Formats and Standards

CycloneDX

An OWASP Foundation project that provides a lightweight SBOM standard designed for application security contexts and supply chain component analysis.

{
  "bomFormat": "CycloneDX",
  "specVersion": "1.4",
  "serialNumber": "urn:uuid:3e671687-395b-41f5-a30f-a58921a69b79",
  "version": 1,
  "components": [
    {
      "type": "library",
      "name": "acme-library",
      "version": "1.0.0",
      "purl": "pkg:npm/acme-library@1.0.0"
    }
  ]
}

Software Package Data Exchange (SPDX)

A standard format for communicating software bill of materials information, including components, licenses, copyrights, and security references.

SPDXVersion: SPDX-2.2
DataLicense: CC0-1.0
SPDXID: SPDXRef-DOCUMENT
DocumentName: example-app-1.0.0
DocumentNamespace: http://spdx.org/spdxdocs/example-app-1.0.0
Creator: Person: Jane Doe (jane.doe@example.com)
Created: 2021-07-01T09:00:00Z

Software Identity (SWID) Tags

ISO/IEC 19770-2 standard that provides identification and management information for software inventory.

<SoftwareIdentity name="Example App"
                  version="1.0.0"
                  tagId="example.com-Example-App-1.0.0">
  <Entity name="Example Corp"
          regid="example.com"
          role="softwareCreator"/>
</SoftwareIdentity>

SBOM Use Cases

Security and Vulnerability Management

Compliance and Risk Management

Operational Benefits

SBOM in Government and Industry Requirements

Executive Order 14028

In May 2021, the U.S. Executive Order on Improving the Nation's Cybersecurity required SBOMs for software sold to the federal government, marking a significant shift toward SBOM adoption.

NTIA Minimum Elements

The National Telecommunications and Information Administration (NTIA) defined minimum elements for an SBOM:

Industry-Specific Requirements

Various industries are adopting SBOM requirements:

Creating and Maintaining SBOMs

Generation Methods

Automated Tools

Continuous Integration

Verification and Validation

Distribution and Consumption

SBOM Best Practices

Implementation Strategy

  1. Start Small: Begin with critical applications or a representative subset
  2. Choose a Standard: Select an SBOM format that meets your needs (CycloneDX, SPDX)
  3. Automate Generation: Integrate SBOM creation into your build process
  4. Establish Governance: Define policies for SBOM creation and maintenance
  5. Build Awareness: Educate teams about the importance and use of SBOMs

Depth and Breadth Considerations

Common Challenges

The Future of SBOMs

Emerging Trends

Integration with Other Security Frameworks