SBOM service for the Cyber Resilience Act
From 11 December 2027, every product that falls under the Cyber Resilience Act and is newly placed on the market needs a list of its software components. You then have to keep an eye on new vulnerabilities in these components for years. We take over this technical part for small manufacturers of software, devices and machines: we create the software bill of materials (SBOM) of your product, check it every month for known vulnerabilities and send you a short report with an update recommendation.
The service is in preparation. Join the waiting list and we will let you know when it launches.

You will be speaking with Ing. Thomas Grafenau, BSc MSc. He leads the intro call and is building the SBOM service.
12 years of software development for mid-sized companies
Does the Cyber Resilience Act apply to me?
The CRA applies to products that are software or contain software and can connect to another device or a network, by cable, radio or the internet. The product also has to be offered in the EU as part of a business, for money or free of charge (Art. 2 and 3 CRA). Typical examples:
- A machine with control software that your service team accesses via remote maintenance.
- A measuring device or sensor that sends data to a computer by radio or cable.
- A desktop or mobile app that you sell or offer free of charge.
- Firmware or a software component that you supply to other manufacturers.
If a machine falls under the Machinery Regulation (EU) 2023/1230 and is also a product with software and a data connection, it has to meet both regulations (Recital 53 CRA).
Devices that cannot connect to anything are not covered, nor are areas with their own rules, such as medical devices and motor vehicles (Art. 2 CRA). As the manufacturer, you decide whether your product falls under the CRA.
More in the Cyber Resilience Act overviewWhat the Cyber Resilience Act requires of you
Three points from Regulation (EU) 2024/2847 that the service addresses:
- Since 11 September 2026, you report actively exploited vulnerabilities and severe incidents having an impact on the security of your product, with an early warning within 24 hours via the ENISA single reporting platform (Art. 14 and Art. 71(2) CRA).
- From 11 December 2027, the remaining obligations apply to products you place on the market from then on, including security updates throughout the support period, which is usually at least five years (Art. 13 and 71 CRA).
- Each of these products needs a software bill of materials (SBOM) in a commonly used, machine-readable format, covering at least the top-level dependencies. It goes into your technical documentation; you do not have to publish it (Annex I, Part II, point 1 and Recital 77 CRA).
What the service takes over
Create the SBOM
We create the software bill of materials of your product in a commonly used, machine-readable format. What we need from you for this, we clarify beforehand.
Check every month
Every month we compare the components with the public vulnerability database OSV. New vulnerabilities also come to light in components that looked harmless when the product was sold.
Report
You receive a short report in plain language: which component is affected, whether attacks on the vulnerability are publicly known and which advisories have been published about it.
Update recommendation
For every finding we recommend the update that closes the gap, with a rough estimate of the effort.
What a report looks like
Example with made-up components. It does not come from a customer and names no real vulnerabilities.
Example product: machine control with remote maintenance, version 4.2 · 186 components checked · 3 findings
| Component | Finding | Actively exploited? | Recommended update | Effort |
|---|---|---|---|---|
| Encryption library A, version 1.1.0 | A bug allows the encrypted remote maintenance connection to be read. | Yes, attacks have been publicly reported | To version 1.1.4 | Low: swap the version, test remote maintenance |
| User interface B, version 3.8.0 | Input in the control panel is not fully validated. | No | To version 3.9.2 | Medium: retest the user interface |
| Image library C, version 0.9.5 | Crash on manipulated image files. Your product does not use this function. | No | No update needed, recorded as not affected | None |
Recommendation: schedule the update of encryption library A first. Because attacks on it are known, also check whether a report under Art. 14 CRA is required.
In the report, “actively exploited” means: a public source reports attacks on this vulnerability. Whether your product is affected and a report is due is for you to assess.
What we take over
We create the SBOM of your product, check it every month and write you the report and the update recommendation.
What stays with you
You decide whether your product falls under the CRA and into which class. The risk assessment, reports to ENISA and installing the updates stay with you. As the manufacturer, you issue the declaration of conformity yourself.
No legal advice: this page and the service do not replace a legal review. Whether and how the Cyber Resilience Act affects your product is for you to clarify with your legal adviser.
Questions and answers
What does the service cost?
We will announce the price at launch. Those on the waiting list hear it first.
When does the service start?
There is no launch date yet. Those on the waiting list hear it first.
What do you need from us?
Typically one of three routes: access to the source code, access to the build, meaning the process that turns the source code into your deliverable software, or an image of your firmware. What fits your product and where the data is kept, we clarify with you beforehand.
Does this also work for controllers and embedded software?
We clarify that in the intro call, using your product. For firmware the bill of materials is often more work than for an app, because libraries there are frequently built firmly into the software.
Does the service replace the declaration of conformity?
No. We deliver the SBOM, the check and the report. As the manufacturer, you issue the EU declaration of conformity yourself and thereby take responsibility for your product (Art. 28(4) CRA).
Talk about your product first
In the intro call we look at which software is inside your product and what an SBOM needs for it, controllers and firmware included. Free and without obligation.
Waiting list
The service is in preparation. Sign up and we will write to you as soon as it launches, and you will hear the price first.