Cybersecurity

EU Cyber Resilience Act SBOM: A Practical Engineering Workflow

Software engineer reviewing code on a laptop for cybersecurity risks

Photo by Dan Nelson via Unsplash, used under the Unsplash License.

Quick answer: An SBOM is a structured inventory of software components and their relationships. Under the EU Cyber Resilience Act (CRA), manufacturers of products with digital elements must identify and document components and vulnerabilities, including an SBOM in a commonly used, machine-readable format covering at least top-level dependencies. The practical value is not the file alone: teams need ownership, version accuracy, vulnerability intake, risk decisions, updates and evidence across the support period.

Why this matters in November 2026

Regulation (EU) 2024/2847 is in force. The CRA reporting obligations for actively exploited vulnerabilities and severe security incidents began applying on 11 September 2026. The main obligations apply from 11 December 2027. Organisations placing connected products on the EU market should therefore build repeatable evidence now rather than waiting for the final application date.

This guide is an engineering workflow, not legal advice. Confirm scope, role and product classification with qualified compliance counsel and the current official text.

What counts as a product with digital elements?

The CRA applies broadly to products with digital elements made available on the EU market when their intended or reasonably foreseeable use includes a direct or indirect logical or physical connection to a device or network. Examples may include industrial gateways, connected controllers, network appliances, smart energy devices, software products and embedded systems.

There are exclusions and interactions with sector-specific legislation. Do not decide scope from a product name alone. Record the intended purpose, connectivity, economic-operator role, market route and applicable sector rules.

What an SBOM contains

An SBOM should identify components sufficiently to support vulnerability and lifecycle work. Common fields include component name, version, supplier, unique identifier, dependency relationship, licence and the product build in which the component appears. The CRA text requires at least top-level dependencies; operational teams often need deeper visibility when a transitive library creates real exposure.

FieldOperational questionExample
ComponentWhat software is included?OpenSSL
VersionWhich release is in this build?Exact package version
SupplierWho maintains or distributes it?Project or vendor identity
IdentifierCan tools match advisories reliably?Package URL or CPE where appropriate
RelationshipHow did it enter the product?Direct or transitive dependency
Build referenceWhich shipped product contains it?Model, firmware and build hash

SBOM formats: choose interoperability, not fashion

CycloneDX and SPDX are widely used machine-readable formats. The right choice depends on customer requirements, build tooling, component ecosystem and downstream analysis. A JSON or XML file that no process validates is not useful evidence. Define a schema version, required fields and validation gate.

Generate the inventory as close to the reproducible build as possible. Repository manifests alone can miss vendored libraries, generated assets, operating-system packages and components introduced during container assembly.

A seven-step engineering workflow

  1. Define the product boundary. Include firmware, applications, containers, operating-system packages, installers and bundled services relevant to the shipped product.
  2. Generate during the build. Use deterministic tooling and retain the build identifier.
  3. Validate quality. Reject unknown versions, missing suppliers and components that cannot be related to the released artefact.
  4. Store immutably. Link the signed release, SBOM, source revision and build evidence.
  5. Monitor vulnerabilities. Correlate advisories with actual versions and reachable functionality.
  6. Triage risk. Record exploitability, exposure, compensating controls, decision owner and deadline.
  7. Update customers and evidence. Distribute fixes securely and maintain records through the support period.

Worked example: an industrial gateway

Assume a manufacturer ships an industrial gateway containing a Linux base image, a web interface, an MQTT client and an open-source cryptographic library. The initial scan finds 438 packages and reports 27 vulnerability matches.

A raw count is not a risk decision. The team first links every result to firmware build 4.2.1. Twelve matches belong to packages absent from the final image and are removed as false matches. Nine affect code that is present but not reachable in the product configuration; the team documents the evidence and monitors changes. Five require scheduled updates. One actively exploited issue affects the exposed web service and triggers the incident and reporting workflow.

StageCountRequired evidence
Scanner matches27Tool output and database date
Confirmed in release15SBOM and build hash
Not reachable/configured9Architecture and test evidence
Planned remediation5Owner, version and delivery date
Urgent exploited issue1Incident, notification and fix records

The example shows why “we generated an SBOM” is not a sufficient control. The organisation needs a response path from detection to customer protection.

Vulnerability reporting is not ordinary ticketing

Since 11 September 2026, the CRA reporting obligations apply to actively exploited vulnerabilities and severe incidents affecting product security. The manufacturer needs an intake route, an escalation decision, accurate timing, product identification and authorised submission through the applicable EU reporting mechanism.

Do not send every scanner finding as an exploited vulnerability. Equally, do not leave the decision to an unowned backlog. Define who determines awareness, exploitation status and reporting applicability, and preserve the evidence used.

Third-party and open-source components

The CRA requires due diligence when integrating third-party components, including open-source software. Procurement and engineering should examine maintenance status, security-update history, known vulnerabilities, release authenticity and the ability to receive fixes. A component with no clear maintainer may create support risk even when it has no current CVE.

When a manufacturer identifies a vulnerability in an integrated component, the Regulation includes obligations to address it and, where relevant, inform the component maintainer. Build a coordinated disclosure path before an urgent case occurs.

Do customers receive the full SBOM?

The CRA requires the manufacturer to draw up and retain an SBOM as part of vulnerability handling and technical documentation. That does not mean every detailed internal SBOM must automatically be published to everyone. Decide distribution from legal obligations, customer contracts, security considerations and procurement requirements.

A useful customer response can describe supported machine-readable format, release coverage, update frequency, vulnerability-contact method and controlled access without making unsupported promises.

Procurement checklist for connected engineering products

  • Product and software support period is stated.
  • Security-update delivery and authenticity are defined.
  • Vendor accepts coordinated vulnerability reports.
  • SBOM format, depth and delivery conditions are agreed.
  • Firmware version and build identity are visible.
  • Critical third-party components have maintainers.
  • End-of-support notification is contractual.
  • Incident contacts and response times are documented.
  • Secure configuration and removal of user data are addressed.
  • Replacement or mitigation exists if a component becomes unsupported.

Quality checks before release

  • Rebuild the product and confirm SBOM reproducibility.
  • Compare declared dependencies with the final artefact.
  • Flag missing versions and ambiguous component names.
  • Verify identifiers against advisory matching.
  • Sign or otherwise protect the release evidence.
  • Test the secure-update and rollback process.
  • Record the vulnerability database timestamp.
  • Assign every actionable finding to an owner.

Common failure modes

  • Creating the SBOM once and never updating it.
  • Scanning only source manifests, not the shipped image.
  • Reporting vulnerability counts without exploitability review.
  • Losing the link between an SBOM and an exact release.
  • Ignoring transitive and operating-system dependencies.
  • Buying unsupported components with no update route.
  • Treating compliance as separate from engineering operations.

Frequently asked questions

Is an SBOM the same as a vulnerability scan?

No. The SBOM inventories components; a vulnerability tool correlates those components with advisory data. Both can be wrong if versions or identifiers are incomplete.

Does the CRA apply only to hardware?

No. Its scope includes software and hardware products with digital elements, subject to the Regulation’s definitions, exclusions and role-specific provisions.

When do the main CRA obligations apply?

The main obligations apply from 11 December 2027. Reporting obligations for actively exploited vulnerabilities and severe incidents began on 11 September 2026.

Related ST College guides

Official sources

This article provides technical education, not legal advice. Confirm current official guidance, product scope, classification, conformity route and reporting duties for the specific organisation and product.

Related Articles