Comparison guide
SBOM vs CBOM
Section 524B requires an SBOM in covered cyber-device submissions. Historical cybersecurity-BOM terminology does not replace that software inventory.
Side-by-side breakdown
| Dimension | SBOM | CBOM |
|---|---|---|
| Full name | Software Bill of Materials | Cybersecurity Bill of Materials |
| Coverage | Software components only (libraries, OS, frameworks). | Software + hardware + runtime libraries affecting security posture. |
| Statutory status | Required in covered cyber-device marketing submissions under Section 524B. | Not statutory; a draft-guidance concept that was not carried into final guidance. |
| Standard formats | SPDX or CycloneDX, machine-readable. | Free-form; no adopted standard. |
| Current guidance context | Statutory software inventory plus guidance-recommended supporting information. | Historical terminology; clarify the inventory requested rather than assume a current separate requirement. |
| Today's equivalent | Continues as the primary inventory artifact. | Record relevant hardware and embedded-software context in architecture and inventory evidence. |
When to use which
Use a machine-readable inventory and verify component content, release linkage, and known-vulnerability evidence. SPDX is Blue Goat's default; the FDA does not mandate one named format.
Include available embedded-software and supplier firmware evidence. Document identification limits and connect the inventory to the system architecture; a hardware list alone does not replace the SBOM.
Frequently asked questions
Keep exploring
Ready when you are
Secure your device before it reaches patients.
30-minute strategy session. No cost, no commitment - just answers from people who've supported 275+ FDA submissions, with zero cybersecurity rejections.
