Firmware inventory · Cyber Resilience Act
Know what is inside your firmware.
The reporting obligations of the EU Cyber Resilience Act have applied since 11 September 2026. To meet them, device makers need to know which components their firmware contains and which vulnerabilities really apply. I build that inventory at a fixed price, for small manufacturers without their own security team.
Why not just run a scanner
Version numbers alone produce noise.
Example: OpenWrt 23.05.6 for a TP-Link Archer C7 v2, deliberately an older release. A plain version search returns thousands of matches. What counts is whether the affected code is built into your image and reachable.
- 3,390 matches from the version search
- 33 assessed one by one
- 8 of those actually affect the image
- 1 of 4 actively exploited kernel flaws affects it
The 33 are all matches outside the kernel plus all actively exploited kernel flaws. Of the remaining kernel matches, 1,262 were ruled out with evidence and 2,099 were not assessed individually.
Examples
Three typical starting points
-
“We have Linux firmware but no overview.”
OpenWrt 23.05.6
Checking against the image turns 3,390 version matches into concrete findings: of 33 matches assessed one by one, 8 affect the image.
-
“We build on a microcontroller.”
Tasmota 16.0.0 on ESP32
A binary scanner recognised no components at all. With the linker map, all 140 libraries were named, 134 of them with a version. The NVD returned no matches for ESP-IDF, lwIP and FreeRTOS, so I also work through vendor advisories.
-
“We already have an SBOM.”
Yocto 5.0.21 on BeagleBone
The CVE data in the bundled bill of materials was generated for kernel 6.6.151, but the image contains 6.6.21. As a result, 4,863 matches were wrongly marked as fixed. The reference build is meant for testing, and Yocto itself warns about this mismatch during its CVE check.
All three examples use freely available firmware. No result means a firmware is secure; the reports record what was not assessed individually.
Packages
Three clearly bounded services
-
Firmware inventory
from €1,900 per firmware version
The starting point: one firmware version, fully documented.
- Software bill of materials as CycloneDX, based on BSI TR-03183-2
- Evidence and confidence for every component
- Documented gaps, such as binary blobs
- Assessed vulnerability list with reasons
- Written report in German or English
-
Reporting readiness
from €900
So that nobody has to improvise when a report is due.
- Technical process and roles
- Templates for the early warning (24 hours), notification (72 hours) and final report
- One dry run with your team
-
Monitoring
from €150 per month and product family
Your bill of materials stays in view after the inventory.
- Automatic check against vulnerability databases every working day
- Reviewed alert with a prepared draft
- Reviews at fixed times; the reporting deadline stays with you
All prices in euros. Under § 19 UStG no VAT is charged. The final price depends on the size of the firmware.
What the fixed price needs
As the manufacturer, you normally have what makes an inventory exact. Please provide at least one of these:
- Linker map of the release build
- Build directory or package manifest
- SDK, BSP and toolchain versions
Without such records, a complete bill of materials is not possible. In that case I offer a time-based survey with evidence per component, documented gaps and requests to your suppliers, but no promise of completeness.
What this is not
- No confirmation of CRA conformity and no declaration of conformity
- No legal advice on what applies in your case
- No penetration test or security audit
- No 24/7 on-call service
- No analysis of third-party devices without the rights holder's written permission
Getting started
Tell me in writing what the device is, how the firmware is built and which records exist. You will get a fixed quote or an honest no.