Container Bill of Materials (CBOM) - FOSSA

Container Bill of Materials (CBOM)

A structured inventory that documents all components, dependencies, and configuration details within a container image, enabling enhanced visibility and security throughout the container lifecycle.

What is a Container Bill of Materials (CBOM)?

A Container Bill of Materials (CBOM) is a comprehensive, machine-readable inventory that documents all components, dependencies, and configuration details within a container image. Similar to a Software Bill of Materials (SBOM), a CBOM provides transparency into what's inside a container, but with additional container-specific metadata and context that traditional SBOMs may not capture.

CBOMs enable organizations to understand and track the contents of their container images, identify security vulnerabilities, ensure license compliance, and verify the provenance of container images throughout the software supply chain. As container adoption continues to grow across industries, CBOMs are becoming increasingly essential for maintaining security and compliance in containerized environments.

Components of a Container Bill of Materials

Base Layer Information

Application Components

Container Configuration

Build Information

CBOM Formats and Standards

Container-Specific SBOM Extensions

Many CBOM implementations extend existing SBOM formats with container-specific fields:

CycloneDX Container Extension

{
  "bomFormat": "CycloneDX",
  "specVersion": "1.4",
  "version": 1,
  "components": [...],
  "containers": [
    {
      "type": "container",
      "name": "example-api",
      "image": {
        "registry": "docker.io",
        "repository": "example/api",
        "tag": "v1.2.3",
        "digest": "sha256:abc123..."
      },
      "layers": [
        {
          "digest": "sha256:def456...",
          "size": 14578923
        }
      ],
      "components": [
        {
          "type": "library",
          "bom-ref": "pkg:npm/axios@0.21.1"
        }
      ]
    }
  ]
}

SPDX Container Annotations

SPDXVersion: SPDX-2.2
DataLicense: CC0-1.0
DocumentName: container-example-1.0.0
DocumentNamespace: http://spdx.org/spdxdocs/container-example-1.0.0
Creator: Tool: container-sbom-generator-1.0.0
Created: 2023-07-01T09:00:00Z
Annotation: DocumentRef-container-image
AnnotationType: OTHER
AnnotationComment: containerImage:registry=docker.io,repository=example/api,tag=v1.2.3,digest=sha256:abc123...

Container-Native CBOM Tools

Various tools specifically designed to generate CBOMs for containers:

Use Cases for Container Bills of Materials

Security Vulnerability Management

Compliance and Governance

Container Lifecycle Management

CI/CD Pipeline Integration

Creating and Maintaining CBOMs

Generation Methods

Build-Time Generation

Creating CBOMs during the container image build process:

# Example GitHub Actions workflow
name: Build Container & Generate CBOM

on:
  push:
    branches: [ main ]

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3

- name: Build container image
        run: docker build -t example/api:latest .

- name: Generate CBOM
        run: syft example/api:latest -o cyclonedx-json > cbom.json

- name: Upload CBOM
        run: curl -X POST -F file=@cbom.json https://artifact-registry/upload

Registry-Based Generation

Generating CBOMs from images stored in container registries:

# Extract CBOM from container in registry without pulling
syft registry:docker.io/example/api:latest -o cyclonedx-json > cbom.json

Runtime Analysis

Creating or augmenting CBOMs by analyzing running containers:

# Analyze running container
docker run --rm -v /var/run/docker.sock:/var/run/docker.sock \
  container-analyzer analyze --container-id abc123 --output cbom.json

Verification and Validation

CBOM and Container Security Best Practices

Minimal Base Images

Layer Optimization

Immutable Containers

Continuous Monitoring

CBOM Implementation Challenges

Multi-Stage Builds

Nested Containers

Tooling Limitations

Integration Complexity

Industry Trends and Future Directions

Standardization Efforts

Container Supply Chain Security

Automated Remediation

Container Attestation

Getting Started with CBOMs

Implementation Strategy

  1. Start Small: Begin with high-priority container images
  2. Choose Tools: Select CBOM generation tools compatible with your environment
  3. CI/CD Integration: Automate CBOM generation in your build pipeline
  4. Establish Policies: Define acceptance criteria for container images
  5. Educate Teams: Train developers and operators on CBOM importance

Key Considerations

Relationship to Other Security Frameworks

SBOM and CBOM

CBOMs extend SBOM concepts to address container-specific aspects, with significant overlap but distinct focus areas.

VEX (Vulnerability Exploitability eXchange)

VEX provides additional context about the exploitability of vulnerabilities identified in a CBOM.

SLSA (Supply chain Levels for Software Artifacts)

SLSA provides a framework for ensuring supply chain integrity, with CBOMs serving as a key component for container verification.

DevSecOps Practices

CBOMs integrate with broader DevSecOps practices for securing the entire container lifecycle from development to deployment.