ENISA's Technical Advisory for Software Bill of Materials, published October 2026 by the European Union Agency for Cybersecurity, is a non-mandatory guidance document aimed at organisations — "especially micro-, small and medium enterprises (SMEs) and stewards" — that are early in SBOM adoption. Rather than restating what an SBOM is, it works through three concrete things: the implementation architecture and data flows across a defined SBOM lifecycle, an indicative STRIDE threat model covering the whole SBOM ecosystem (not just the file), and a list of security measures to apply across that ecosystem. ENISA is explicit that this "should not be considered as a legal interpretation" of the Cyber Resilience Act, even though it considers CRA requirements as context.
Key takeaways
- Section 2.1.1 does not invent its own field list.
- Section 2.1.3 then makes a point device makers often miss: the format does not decide what an SBOM contains; when it is generated does.
- Validation — checking the generated SBOM is syntactically correct, conforms to the chosen specification, contains required metadata, and has valid component identifiers (Section 2.2.2).
- This ecosystem-wide framing is the advisory's most distinct contribution: it treats a stolen signing certificate or a compromised repository mirror as SBOM threats in their own right, not just a corrupted file.
Where did this document come from, and what does it leave out?
Per Section 1.3, the current version is the result of ENISA's public "Call for feedback: Advancing software supply chain security together!", which ran from 17 December 2025 to 23 January 2026 and drew 67 contributions from "public and private stakeholders, cybersecurity experts, and the open-source community." That feedback, combined with survey results from ENISA's own SBOM Adoption State of Play 2026, led ENISA to "transform the 'SBOM Landscape Analysis: Towards an implementation guide' into a 'Technical Advisory for Software Bills of Materials'" — a reframing toward practical, lifecycle-based guidance. A further review cycle ran 31 July to 11 September 2026 with the CRA Expert Group's SBOM workstream. The document is released under Creative Commons Attribution 4.0 International (CC BY 4.0) (ISBN 978-92-9204-813-6, doi 10.2824/2077129); the full text is on ENISA's publication page.
Scope is deliberately narrow: Section 1.2 states the advisory is "limited to Software Bill of Materials" and does not cover Hardware BOM, Cryptographic BOM, AI BOM or other emerging BOM variants, which it treats as out of scope "for this advisory." It is "sector-agnostic" and aimed at early-stage adopters rather than organisations assessing their existing SBOM maturity. For a device maker that means the hardware side of a product (chips, modules, boards) sits outside this document, even though it often drives which firmware components ship.
Which data fields does ENISA treat as the SBOM baseline?
Section 2.1.1 does not invent its own field list. Its Table 1 lines up Germany's BSI TR-03183-2 (version 2.1.0) against the US CISA "Minimum Elements for a Software Bill of Materials" (2026 edition), so one SBOM can satisfy both. The two lists overlap on the core and differ at the edges:
| Field group | BSI TR-03183-2 | CISA Minimum Elements |
|---|---|---|
| Who made the SBOM | Creator: email address, or a URL if no email exists | SBOM Author: name of the entity |
| When | Timestamp of compilation; UTC recommended | SBOM Timestamp of the most recent update |
| Document identity | SBOM-URI | SBOM Version, data format name and version |
| Signature and tooling | — | SBOM Author Signature, SBOM Tool Name and Version |
| Generation context | — | Before build, during build or after build |
| Component maker | Component creator: email or URL | Component Producer: name |
| Name and version | Both required | Both required |
| Identifiers | Source code URI, URI of the deployable form, other identifiers such as CPE or Package URL | Component Identifiers |
| Hash | Hash of the deployable component; source hash optional | Component Hash Value plus Hash Algorithm |
| Licence | Distribution and original licences; effective licence optional | Component License |
| Dependencies | Direct dependencies or contained components | Component Dependency Relationship |
| File properties | Filename; executable, archive and structured flags | — |
For firmware, the rows that usually fail are hashes, licences and supplier contact: a binary scan sees a library and a version string, but not who maintains it. See our guides on SBOM Minimum Elements and Package URL identifiers for the field details.
Which formats and SBOM types does it point to?
Section 2.1.2 names SPDX 3.0.1 and CycloneDX 1.7 as the two predominant formats, citing the finding that "almost 73% of the organisations use CycloneDX or SPDX." SPDX's lineage runs through ISO/IEC 5962:2021 (for the 2.2.1 specification) with SPDX 3.0 separately ratified as an OMG standard and now pursuing an ISO update; CycloneDX 1.7 has been "ratified as ECMA-424" by Ecma International and is "currently pursuing ISO JTC1 FastTrack." Our CycloneDX vs SPDX guide compares the two in depth.
Section 2.1.3 then makes a point device makers often miss: the format does not decide what an SBOM contains; when it is generated does. Its Table 3 adopts CISA's six SBOM types:
| SBOM type | Generated from | What it means for firmware |
|---|---|---|
| Design | The intended design of a new artifact | Component choices before code exists |
| Source | Source files and declared dependencies | Exact versions of what the code pulls in |
| Build | The build that produces the release artifact | Transitive dependencies, linked libraries, hashes, supplier data |
| Analysed | Analysis of a built artifact, using heuristics | What a scan of a vendor or legacy image finds; ENISA notes it is also called a "3rd party" SBOM |
| Deployed | Software present on a system | What is installed on a fielded unit |
| Runtime | Instrumenting the running system | Dynamically loaded modules and plug-ins |
A firmware team that controls its build should aim for a Build SBOM and use an Analysed SBOM to check it, or to cover binary blobs it receives from suppliers.
What is the SBOM lifecycle, per ENISA?
Section 2.2.1 lays out a conceptual lifecycle: it "begins with the software build and SBOM generation," then moves through:
Validation— checking the generated SBOM is syntactically correct, conforms to the chosen specification, contains required metadata, and has valid component identifiers (Section 2.2.2). Cryptographic signing— "to protect its integrity and authenticity" before storage. Secure storage— in a repository or registry for downstream consumption. Operational consumption— by security, development, procurement and compliance teams. Maintenance and updates— "the continuous process of keeping the SBOM up-to-date and synchronised with the current version of the software."
Section 2.2 explains why the lifecycle matters with a gap between what SBOM consumers need and get: 36% of survey respondents need all primary components and direct dependencies with declared known unknowns, but only 29% receive them; 24% need full-depth SBOMs and 14% receive them. Section 2.2.2 maps the same lifecycle onto a CI/CD pipeline and reports that 41% of organisations aim to fully automate SBOM generation for each release or build, but only 26% expect to fully automate SBOM updates across a product's entire support period (a further 23% expect to partially automate it) — automation drops off sharply after the initial build. Section 2.2.3 adds that 33% of organisations rely on open-source tooling, listing format-specific generators (cdxgen, Syft, Trivy for CycloneDX; spdx/tools-python, Yocto's built-in SPDX support for SPDX) alongside cross-format converters such as OpenSSF's Protobom. Its Table 4 also lists Linux make spdx and Zephyr west spdx, which matters for embedded teams: see our Yocto and Buildroot SBOM guide.
What does the STRIDE threat model cover?
Section 3.1 applies Microsoft's STRIDE threat-modelling framework — "divided in six categories: Spoofing, Tampering, Repudiation, Information disclosure, Denial of service and Elevation of privilege" — not just to the SBOM document, but to "the entire SBOM ecosystem (e.g., SBOM generation tools, validation and signing service, repositories, consumption pipelines)." Representative scenarios from Table 5:
| STRIDE category | Example threat scenario | Indicative mitigation |
|---|---|---|
| Spoofing | Impersonation of a legitimate SBOM author or software producer to distribute a compromised SBOM | Digital signatures, supplier identity verification |
| Spoofing | Stolen certificates are used to sign a malicious SBOM | Secure key management, certificate revocation |
| Tampering | Components, versions or dependency relationships are added, deleted or altered after generation | Integrity verification, signature verification |
| Repudiation | The software producer or SBOM author denies generating or publishing an SBOM | Digital signatures, timestamps, audit logs |
| Information disclosure | Uncontrolled sharing reveals the technology stack, supplier relationships or exact versions | Controlled SBOM sharing, access control |
| Denial of service | Extremely large or deeply nested SBOMs exhaust parser resources | SBOM size limits, parser hardening |
| Elevation of privilege | Compromised signing infrastructure creates a "trusted" SBOM | Key management, access control |
This ecosystem-wide framing is the advisory's most distinct contribution: it treats a stolen signing certificate or a compromised repository mirror as SBOM threats in their own right, not just a corrupted file.
Which general risks matter most for firmware SBOMs?
Section 3.2's Table 6 lists general risks next to the STRIDE threats. Five of them describe everyday firmware problems:
- Incomplete SBOM — components missing, so vulnerabilities stay hidden. Mitigation: generation at release, CI/CD integration, documented "known unknowns."
- Outdated SBOM — the SBOM no longer matches the shipped version. Mitigation: regenerate on defined triggers.
- Poor component identification — names that do not match across ecosystems. Mitigation: Package URL or CPE with namespace, exact version and hashes.
- Insufficient accuracy — heuristic tools report components that are absent or miss ones that are present, causing "alert fatigue."
- Weak SBOM-to-artifact binding and insufficient retention — the SBOM cannot be tied to the exact image, or old SBOMs are gone when a new CVE lands. Mitigation: bind with a hash or immutable digest and "retain SBOMs per release."
The same table lists "lack of vulnerability prioritization" and suggests combining SBOM data with VEX; see our CycloneDX VEX guide.
Which security controls go with each lifecycle phase?
Section 4.2's Table 7 assigns specific controls to specific lifecycle phases rather than listing generic advice: Role-based Access Control, Multi-factor Authentication, Least Privilege and TLS 1.3 transport security apply across "all phases"; generation gets trusted-repository sourcing and provenance generation, with tool-stack verification listed among the controls for all phases; validation, signing and storage get secure secrets management, artifact binding (cryptographically associating the SBOM with the artifact it describes) and tamper-evident, version-controlled storage; and maintenance gets version control plus backup and recovery for SBOMs, signing material and audit logs. Section 4.1 separately recommends starting with build-time integration ("the foundation... requires minimal infrastructure changes") before adding event-triggered generation (webhooks on commit, PR or release events) — and insists organisations document "known gaps, exceptions and 'known unknowns'" where dependencies can't be identified or binary-only components can't be fully analysed, rather than presenting an SBOM as complete when it isn't.
How does the advisory relate to the CRA's SBOM text?
Section 1.1 is direct about the limit of its own authority: it "considers regulatory requirements such as those set out in the Cyber Resilience Act (CRA)... but essentially describes recommended best practices that may go beyond those requirements," and "should not be considered as a legal interpretation of the CRA." Section 1.2 restates that its recommendations "are non-mandatory and do not create or modify any legal, regulatory, or compliance obligations." The legal obligations sit in the regulation itself:
| CRA provision | What it says about SBOMs |
|---|---|
| Article 3(39) | Defines an SBOM as "a formal record containing details and supply chain relationships of components" in a product's software |
| Annex I, Part II, point (1) | Manufacturers draw up an SBOM "in a commonly used and machine-readable format covering at the very least the top-level dependencies" |
| Article 13(24) | The Commission may specify the SBOM's format and elements by implementing act |
| Annex VII, point 2(b) | The SBOM is part of the technical documentation on vulnerability handling |
| Annex VII, point 8 | A market surveillance authority can request it with a reasoned request |
| Annex II, point 9 | If the manufacturer shares the SBOM with users, the user information says where to find it |
Per Article 71(2), these obligations apply from 11 December 2027. The CRA floor is top-level dependencies; the advisory's lifecycle, signing and retention practices go beyond it. Our CRA Annex I guide and firmware SBOM guide cover the legal side.
How would a device maker apply it to one firmware release?
Worked example (synthetic; product and numbers are invented for illustration). A maker of an industrial gateway builds firmware 3.2.0 with Yocto:
Generatea Build SBOM with Yocto's SPDX output during the release build, and note the generation context (during build). Checkit with an Analysed SBOM: scan the final image with a binary tool. Here the scan finds 214 components against 198 in the build SBOM; the 16 extra are a vendor Wi-Fi blob and its libraries. Record known unknowns:the blob's internal components cannot be resolved, so the SBOM states that gap instead of omitting it. Validateschema, required fields and identifiers (Package URL where possible, CPE for the vendor blob). Sign and bind:sign the SBOM and record the image's SHA-256 digest in it. Storeit next to the image in a version-controlled repository, with access control. Consume:match components against vulnerability sources; route findings into remediation timelines. Retain and regenerate:keep the 3.2.0 SBOM after 3.3.0 ships, so a new CVE can be checked against every supported release.
What are the common pitfalls?
- Treating the CRA's "top-level dependencies" minimum as the target, then failing a customer who asks for BSI TR-03183-2 depth.
- Shipping an Analysed SBOM from a scan as if it were a Build SBOM, without saying which it is.
- Signing the SBOM but not binding it to the image digest, so it cannot be matched to a unit in the field.
- Regenerating the SBOM for each release but deleting older ones, so fielded versions cannot be checked.
- Publishing full SBOMs openly when the advisory's information-disclosure threats call for controlled sharing.
Where do a firmware scanner and AI fit in this lifecycle?
SoftWSP covers part of ENISA's consumption phase and adds an Analysed SBOM. It extracts the components it can identify from a built firmware image and writes them as a CycloneDX 1.6 JSON SBOM labelled with the post-build lifecycle phase; it does not invent hashes, licences or supplier fields the image does not reveal, and it does not sign the SBOM, generate it inside your build, or re-match every release automatically. It matches the components against NVD, CISA KEV, FIRST EPSS and CISA CSAF ICS advisories, and AI drafts a cited report that an engineer reviews before it ships; watchlist alerts can follow a CVE ID or a vendor and product. AI does not generate, sign or validate the SBOM, and it does not decide what counts as a disclosed gap. VEX statements and reachability judgements stay with your engineers. See device & firmware security.
This guide summarises ENISA's Technical Advisory for Software Bill of Materials (October 2026); it is not a substitute for the full text and does not constitute compliance or legal advice.
Put this guide to work
Frequently asked questions
What is ENISA's Technical Advisory for Software Bill of Materials?
A non-mandatory guidance document published by the European Union Agency for Cybersecurity (ENISA) in October 2026 (ISBN 978-92-9204-813-6, doi 10.2824/2077129), aimed at organisations — "especially micro-, small and medium enterprises (SMEs) and stewards" — that are "seeking to set up the initial capabilities to enhance the software supply chain transparency." Per its own Section 1.1, it (1) "outlines the SBOM implementation architecture and data flows based on a defined lifecycle," (2) "presents an indicative SBOM threat model along with targeted risks," and (3) "lists measures to address the security issues across the SBOM ecosystem." It replaces an earlier working title, "SBOM Landscape Analysis: Towards an implementation guide," after ENISA ran a public call for feedback (17 December 2025 to 23 January 2026) that drew 67 contributions, plus a further review by the CRA Expert Group's SBOM workstream (31 July to 11 September 2026). It is released under Creative Commons Attribution 4.0 International (CC BY 4.0).
What SBOM lifecycle phases does ENISA describe?
Section 2.2.1 describes the lifecycle as beginning "with the software build and SBOM generation based on the necessary sources of information," then progressing through: SBOM validation ("to assess the quality of the generated SBOM"), cryptographic signing ("to protect its integrity and authenticity"), secure storage, operational consumption, and "continuous maintenance and updates." Section 2.2.2 maps the same phases onto a CI/CD pipeline, and reports from ENISA's own SBOM Adoption State of Play 2026 survey that 41% of organisations aim to fully automate SBOM generation per release/build, while only 26% expect to fully automate — and a further 23% to partially automate — SBOM updates across a product's entire support period.
What does the advisory's STRIDE threat model cover?
Section 3.1 applies Microsoft's STRIDE threat-modelling framework — "divided in six categories: Spoofing, Tampering, Repudiation, Information disclosure, Denial of service and Elevation of privilege" — to the whole SBOM ecosystem, not just the SBOM file itself: it explicitly scopes threats across "SBOM generation tools, validation and signing service, repositories, consumption pipelines." Worked examples include spoofed SBOM authors, spoofed CI/CD pipelines and spoofed generation tools (Spoofing); altered component versions, hashes or provenance data (Tampering); and unauthorised disclosure of technology stack, supplier relationships or dependency graphs through uncontrolled SBOM sharing (Information disclosure) — each with indicative mitigations such as digital signatures, build attestations, and SBOM signature verification.
What SBOM formats and data-field baselines does the advisory point to?
Section 2.1.2 names SPDX and CycloneDX as the two predominant machine-readable SBOM formats, citing the SBOM Adoption State of Play 2026 survey finding that "almost 73% of the organisations use CycloneDX or SPDX," and giving their current versions as SPDX 3.0.1 and CycloneDX 1.7. For data fields, Section 2.1.1 maps Germany's BSI TR-03183-2 required fields against the fields in the US CISA-led Minimum Elements for a Software Bill of Materials (see our [SBOM Minimum Elements guide](/guides/sbom-minimum-elements/)) as "a baseline for generating SBOMs" that satisfies both. Our [CycloneDX vs SPDX guide](/guides/cyclonedx-vs-spdx-sbom-formats/) covers the two formats' standards-body status and capabilities in more depth.
Does following this advisory satisfy the EU Cyber Resilience Act's SBOM requirement?
Not on its own, and the document says so directly. Section 1.1 states the advisory "considers regulatory requirements such as those set out in the Cyber Resilience Act (CRA)" but "essentially describes recommended best practices that may go beyond those requirements," adding explicitly: "this document should not be considered as a legal interpretation of the CRA." Section 1.2 reinforces that "the recommendations and best practices described herein are non-mandatory and do not create or modify any legal, regulatory, or compliance obligations." A manufacturer should still check the CRA's own Annex I SBOM text (see our [firmware SBOM guide](/guides/firmware-sbom/)) for what is actually legally required.
Sources
- ENISA: Technical Advisory for Software Bill of Materials — publication page
- ENISA Technical Advisory for Software Bill of Materials, full-text PDF (v1.10, October 2026)
- ENISA: SBOM Adoption State of Play – 2026 — publication page
- Regulation (EU) 2024/2847 (Cyber Resilience Act), EUR-Lex
- BSI: Technical Guideline TR-03183 Part 2 — Software Bill of Materials
- Ecma International: ECMA-424, CycloneDX Bill of Materials Specification
- The SPDX Specification, version 3.0.1
About this guide
SoftWSP Firmware Security Desk
Covers the SBOM cluster: 31 guides.

In this cluster
Questions about this page?
