Skip to main content
    DevOps
    Way of Working
    1. Home
    2. Capabilities
    3. Cicd Sbom

    SBOM Generation

    Foundation
    Phase: build
    DF
    LT

    Quick Reference

    Phase
    build
    Epic
    CI/CD & Build Automation
    Milestone
    Foundation
    Target
    >= 80% builds generate SBOM
    Implementation Time
    Part of CI/CD & Build Automation epic: 3.5 weeks (23 hours per capability avg)

    What & Why

    Definition

    >= 80% of builds generate Software Bill of Materials (SBOM) in SPDX or CycloneDX format.

    Business Value

    Reduces manual build time from 2 hours to 10 minutes and enables 3-5x more frequent integration testing through automated pipeline execution Achieving >= 80% builds generate SBOM is a key milestone toward this goal.

    Context

    This capability is part of the Foundation milestone's focus on establish baseline practices (testable, releasable, monitorable). Essential for teams targeting DF, LT improvements.

    Success Criteria

    Target

    >= 80% builds generate SBOM

    Measurement

    SBOM file presence in build artifacts

    Evidence

    • SBOM generation tool config
    • Sample SBOM files
    • Vulnerability tracking linked to SBOM

    In Practice

    Real-World Implementation

    CI pipeline runs syft or cyclonedx-cli to generate SBOM, uploads to artifact registry alongside Docker image.

    Concrete Example

    Build generates sbom.spdx.json: 247 dependencies listed with CPEs, licenses. SBOM stored in registry.company.com/user-service:1.3.2/sbom.spdx.json.

    Implementation Guide

    Prerequisites

    Artifact Versioning
    100% builds produce versioned artifacts

    Implementation Steps

    Follow the measurement approach: SBOM file presence in build artifacts

    For detailed step-by-step guidance, refer to the CI/CD & Build Automation Implementation Kit.

    Resources

    Implementation Kit

    CI/CD & Build Automation Kit

    Templates

    Browse all templates

    Related Resources

    View learning paths

    Related Capabilities

    Prerequisites

    Implement these first

    Artifact Versioning

    Enables

    What this unlocks

    Supply Chain Verification
    SLSA Provenance Generation

    Complementary

    Often adopted together, from the CI/CD & Build Automation epic

    CI Pipeline Template
    Automated Security Scanning
    Secrets Detection
    Fast Feedback Loop

    Troubleshooting & FAQs

    Common Issues

    Issue: Target metric not improving

    Solution: Verify measurement is accurate, check if prerequisites are fully implemented, review evidence artifacts for completeness

    Issue: Team resistance to adoption

    Solution: Start with pilot team, demonstrate value with metrics, provide training and support during transition

    Issue: Inconsistent implementation across teams

    Solution: Create shared templates and guidelines, establish regular sync meetings, use automation to enforce standards

    Frequently Asked Questions

    Can we implement this before completing prerequisites?

    While possible, it's not recommended. Prerequisites ensure foundational practices are in place, making this capability more effective and easier to adopt.

    How long does implementation typically take?

    Most capabilities can be implemented within 90 days when tackled as part of the Foundation milestone. Individual timelines vary based on team size and existing practices.

    DevOps
    Way of Working

    DevOps practices for the entire delivery lifecycle

    © 2019-2026 devopswow.com. Created by Burhan Öcüt

    PartnersAboutPrivacyTermsCookies