sbomlisted

# SBOM ## Purpose Create a software bill of materials (SBOM) that delivers actionable, measurable results. **Category**: Cybersecurity & Information Security ## Inputs ### Required - **Objective**: What you want to achieve with this deliverable - **Context**: Relevant background information (systems, scope, environment) ### Optional - **Constraints**: Any limitations or requirements to consider - **Existing Work**: Previous documents or data to build on ## Context Before starting, read the repo's `CLAUDE.md` and any relevant notes under `memory/` (e.g. `memory/repo/<repo>/`, `memory/feedback/`) for prior decisions and constraints. ## Process ### Step 1: Context & Research - Review any existing software bill of materials (sbom) documents in the project - Identify key stakeholders and their requirements - Select the most appropriate framework: NTIA Minimum Elements, CISA SBOM Guidance, CycloneDX ### Step 2: Analysis & Framework Application - Apply the selected framework to structure the software bill of materials (sbom) - Identify gaps, opportunities, and risks - Define success metrics: Component Count, Known Vulnerability Count (CVEs), License Compliance Rate, SBOM Freshness - Document assumptions and dependencies - Validate approach against industry best practices ### Step 3: Build the Deliverable - Structure the software bill of materials (sbom) using the output format below - Include specific, actionable recommendations — not generic advice - Add concrete number