The EU’s Cyber Resilience Act (CRA) sets a number of requirements for “products with digital elements” – and this covers most things nowadays. The CRA will come into force any day now, and thus a need for certification arises – how can you prove that you comply with the requirements?
The standard ETSI EN 303 645 is considered by many to cover the security requirements set by the CRA. In TELEMETRY, we have developed several tools that can be used to test individual requirements in the standard, and that can therefore be advantageously included in a certification process. I will not try to cover the entire standard here, but give some quick examples.
Provision 5.13-1B Data input […] shall be validated by the device regarding unexpected data input to prevent system manipulations and failures.
Our approach to this requirement is to use network fuzzing. We have taken the Boofuzz fuzzer (open source) as a starting point, and configured a test environment adapted to fuzzing wireless home routers. Read more about this here: https://www.ntnu.no/ojs/index.php/nikt/article/view/6241
Provision 5.2-3 Manufacturers should continually monitor for, identify and rectify security vulnerabilities within consumer IoT products they sell […]
Our SBOM tool identifies software components of a device and uses the resulting overview to pull down relevant vulnerabilities from the National Vulnerability Database (NVD). The tool can be run as part of a test process, but can also be run periodically while equipment is in operation.

Provision 5.3-8 Security updates shall be timely.
By using the SBOM tool in tandem with the risk assessment tool Spyderrisk, we can prioritise vulnerabilities so that the most critical ones can be patched first.
We create a model of the system in Spyderrisk, and use the SBOM tool to download all relevant vulnerabilities. Spyderrisk then runs through the list and “implements” the vulnerabilities one by one to assess how it affects the risk level. After all the vulnerabilities have been assessed in this way, you know which vulnerability carries the most risk, and you can deal with this first. Read more about this here: https://jaatun.no/papers/2025/CVE_pri_ARES_WS.pdf
This article was originally published at Infosec Sintef.
