An industrial software bill of materials is useful only when it is tied to a specific machine and released software baseline. PLC projects, HMI applications, gateway runtimes, operating-system packages, libraries, drivers and vendor components have different levels of transparency, so the record must show both known components and explicit gaps without pretending a manual inventory is complete.
The short answer
Define the SBOM subject: one released machine/software configuration with a stable identifier and version. Obtain supplier SBOMs where available and generate source/build/deployed information only with approved tools and access. Record author, producer, component name and version, identifiers, hash where available, license, dependency relationship, tool, timestamp and generation context, plus the exact machine/project/revision it describes. Include proprietary binaries and firmware at the level legitimately supplied, mark unknown or unresolvable components, protect sensitive distribution, and link advisories and VEX without rewriting historical SBOMs. Issue a new controlled SBOM whenever the released software baseline changes.
- State the SBOM subject, type, coverage and known unknowns explicitly.
- Prefer machine-readable standard formats while preserving supplier-original evidence.
- Link each SBOM to an immutable released artifact or deployed baseline.
- Control access because component detail can be commercially or operationally sensitive.
Decision guide
| SBOM view | What it represents | Industrial use |
|---|---|---|
| Design/source | Intended or source-level components and dependencies | Engineering review and supplier transparency |
| Build | Components observed during creation of the release artifact | Release provenance and vulnerability triage |
| Analyzed | Components inferred from a binary or package by analysis | Gap reduction when source/build data are unavailable |
| Deployed | Software actually present on a machine or system | Installed-base exposure and maintenance decisions |
A practical workflow
- 01
Define subject, owner, audience, access classification, format, type and minimum fields.
- 02
Collect supplier records and approved generated evidence; identify PLC, HMI, OS, runtime, libraries, drivers and firmware.
- 03
Normalize identifiers without discarding originals, map dependencies and declare coverage and known unknowns.
- 04
Validate structure, component identity, version, hashes and linkage to the released machine baseline.
- 05
Publish securely, correlate advisories and VEX, and issue a new revision whenever the baseline changes.
Evidence and acceptance
Retain SBOM subject and stable identifier, machine/project and release revision, SBOM author and supplier, format/schema/tool versions, generation context and timestamp, component names, versions, identifiers, hashes, licenses and dependencies, firmware and proprietary-component statements, coverage, known unknowns, source artifacts, validation results, access classification, approval, distribution record, advisory/VEX links, installed-base mapping and supersession history.
Common mistakes
- Calling a manually typed software list a complete SBOM without coverage and gaps.
- Publishing component detail publicly without considering supplier terms and operational sensitivity.
- Mixing components from several machine revisions into one unversioned document.
- Discarding supplier identifiers or original SBOMs during normalization.
- Editing an old SBOM after a release instead of issuing a new linked revision.
Responsibility boundary
Primary sources
Technical claims and product boundaries were checked against these primary sources. Fact-checked
Frequently asked questions
Is an installed-software register the same as an SBOM?
No. It is useful evidence, but an SBOM also describes a defined software subject, component identities and dependency relationships with stated coverage.
What if the PLC vendor does not provide component detail?
Record the supplied product and version accurately, retain vendor evidence and declare the component-level gap rather than inventing detail.
Should an SBOM be public?
Not automatically. Distribution should follow legal, supplier, cybersecurity and operational-sensitivity rules for its intended consumers.
Does AutoNexit create or scan SBOMs?
No. It can preserve approved SBOM files and their relation to equipment and releases, but it does not analyze software.