# Do SaaS products need an SBOM under the Cyber Resilience Act?

URL: https://sbombox.com/blog/sbom-for-saas-cra
By SBOMBox SBOM experts. Published 2026-11-11

> Pure SaaS is generally outside the CRA, but downloadable agents, apps and remote data processing can bring parts of your product in scope. How to draw the line.

Short answer: a pure software-as-a-service product is generally outside the Cyber Resilience Act, so the CRA does not require an SBOM for it. But anything you ship to customers (an agent, a desktop or mobile app, an SDK, firmware) is a product with digital elements and is in scope, and so is remote data processing that a product needs to work.

## Why SaaS is mostly out

The CRA regulates products with digital elements made available on the EU market. Online services are covered by other law, notably NIS2. Industry groups such as BSA have urged ENISA to keep SaaS clearly out of the SBOM requirement, partly because a published SBOM for a hosted service could reveal attack surface that is not visible today.

## Where SaaS companies get pulled in

- Downloadable components: CLIs, desktop clients, browser extensions, mobile apps, on-premises agents and SDKs.
- Remote data processing solutions: back-end processing designed by the manufacturer, without which the product could not perform one of its functions.
- Hardware you sell or bundle, even if most of your value is in the cloud.

If one of these applies, that component needs CRA conformity, including an SBOM in its technical documentation. See [does the CRA apply to my company?](https://sbombox.com/blog/does-the-cra-apply-to-my-company).

## Why you may want an SBOM anyway

- Enterprise buyers increasingly ask for one in security questionnaires, whatever the law says.
- NIS2-regulated customers have to manage supply-chain risk and will push requirements onto suppliers.
- When the next Log4Shell lands, an SBOM per deployment is how you answer 'are we affected?' in minutes.

## A pragmatic approach

- Inventory everything you ship to customers' machines. Treat those as CRA products.
- Generate an SBOM for each service as well, but keep it internal or share it under NDA.
- Use VEX to answer customer CVE questions without exposing the full inventory.
- Write down your reasoning about what is and is not in scope, and review it each year.

## Examples

- A project-management web app with no downloads: generally out of scope. Keep an internal SBOM for incident response.
- The same app with a desktop client and a CLI: the client and CLI are CRA products and need SBOMs.
- A smart-thermostat company whose device cannot work without its cloud back end: the back end can count as remote data processing for the device.

Small team? Our [30-minute compliance plan](https://sbombox.com/blog/compliance-plan-for-startups) covers the first steps, and the Free plan includes 3 projects.

This is general information, not legal advice. Confirm how the rules apply to your products with counsel.
