What it is
A software bill of materials (SBOM) is a structured inventory of software ingredients. SPDX and CycloneDX define ways to exchange that inventory between tools and organizations. They are separate specifications, so a delivery agreement must identify which format and version the recipient accepts.
For an automotive project, an SBOM can describe software inside an ECU image, an application, or an update package. Its value comes from linking component information to a specific delivered artifact. An inventory for a source repository may differ from the software included in the production image.
Who it applies to
These formats are useful to vehicle manufacturers, ECU suppliers, software vendors, integrators, and teams operating vulnerability management or software logistics systems. They are not automotive regulations and do not independently require every supplier to deliver an SBOM. Obligations arise from contracts, organizational policies, or applicable requirements.
Software teams usually produce the inventory; cybersecurity teams investigate exposure; release and update teams preserve its connection to delivered software. Suppliers and customers need a shared agreement on inventory scope, required fields, and acceptance checks.
What it covers
Both formats represent components and relationships, with metadata that helps recipients identify and assess software. Their capabilities extend beyond a simple package list, but supported fields and representations depend on the selected version.
| Information | Automotive use |
|---|---|
| Component names, versions, and identifiers | Identify libraries included in an ECU release |
| Dependency relationships | Trace software incorporated through other components |
| License and supplier information | Support license review and supplier clarification |
| Hashes and provenance information | Help connect inventory records to artifacts and origins |
SPDX has established roots in license information exchange and supports broader software supply chain information. CycloneDX supports component inventories and related security information, including vulnerabilities and cryptographic assets. Neither format guarantees that an inventory is complete, accurate, or sufficient for a particular customer.
How it fits with other documents
An SBOM supports cybersecurity engineering and monitoring activities associated with ISO/SAE 21434 and UNECE R155. It can help teams investigate which delivered products contain an affected component. It does not establish compliance with either document by itself.
For software logistics and updates, inventories complement release manifests, configuration records, and processes associated with ISO 24089 and UNECE R156. A release manifest identifies what is delivered; an SBOM describes its software composition.
Vulnerability Exploitability eXchange (VEX) information adds an assessment of whether a vulnerability affects a particular product. Finding a component in an SBOM does not, by itself, prove exploitability. Likewise, license metadata supports review without replacing legal assessment.
In practice
Define the SBOM delivery contract before integrating supplier software. Specify the format, version, inventory boundary, component identification rules, dependency detail, and treatment of modified or proprietary components.
Generate the inventory during the build and reconcile it with the packaged output. Include relevant vendor binaries and embedded libraries that package managers may miss. Validate both schema conformance and content quality: a structurally valid document can still omit important dependencies.
Store the accepted SBOM alongside the release artifact and retain their association through ECU reprogramming and OTA campaigns. When a vulnerability is reported, use it to identify candidate releases, then confirm applicability using configuration details and engineering evidence. Regenerate the inventory when composition changes, and check conversions between SPDX and CycloneDX for lost information.