SBOM Formats: SPDX, CycloneDX, and SWID
What You'll Learn
You'll understand the three major SBOM standards, how they differ structurally, and which to choose for your use case.
Why Multiple Formats Exist
Just as there are different file formats for images (JPEG, PNG, SVG), there are different formats for expressing what components make up your software. Each SBOM format solves similar problems but with different priorities and communities behind them.
The Three Major Standards
SPDX (Software Package Data Exchange)
Origin: Linux Foundation, ISO/IEC standard
Strengths: Comprehensive licensing data, broad industry adoption, legal focus
Format: JSON, YAML, RDF, tag-value
Best for: License compliance, legal review, open-source governance
Think of SPDX as the "passport" format—highly detailed, internationally recognized, focused on identity and legal status.
CycloneDX
Origin: OWASP project
Strengths: Security-focused, vulnerability tracking, lightweight
Format: JSON, XML
Best for: Security scanning integration, vulnerability management, rapid iteration
CycloneDX is like a "medical record"—optimized for tracking health (security) status and changes over time.
SWID (Software Identification Tags)
Origin: ISO/IEC standard, NIST
Strengths: Asset management, inventory tracking
Format: XML
Best for: Enterprise asset inventory, compliance frameworks
SWID tags are like "barcodes"—designed for tracking and inventory across large organizations.
Choosing the Right Format
- License compliance is critical? → SPDX
- Vulnerability tracking is priority? → CycloneDX
- Government/enterprise asset management? → SWID
- Unsure? → Both SPDX and CycloneDX have strong tooling and growing adoption
Many organizations generate multiple formats from the same source data, since conversion tools exist.
Key Takeaway: SPDX focuses on licensing, CycloneDX on security, and SWID on inventory—choose based on your primary need, or generate multiple formats for comprehensive coverage.