Skip to content

EU 2024/2847 (CRA) · Article 14 reporting has applied since 11 September 2026

One CRA platform for every connected device

SBOM, vulnerability management, the technical file and Article 14 notifications in one product record, and signed updates to your devices through one SDK. Upload your firmware; the records the CRA asks for build up as you work.

Fig. 1 · Shell model

Hover or tap a plate.

Platform

From design to notification, in one record

Class and risk decisions, the components in the SBOM, vulnerability decisions and the documents come together in one product record. It works whatever chip you use: start from a firmware image, an SBOM or a component list.

01 · Design

Class, Risk and Annex I

A test that determines the product's CRA class, the conformity assessment routes of Article 32 and a risk assessment. For each of the 22 essential requirements in Annex I you record your decision and your evidence. A readiness path per product shows the next step.

  • Product class test under Annexes III and IV, conformity assessment routes under Article 32
  • Risk assessment with threats and residual risk
  • Decision and evidence for the 22 requirements of Annex I (14 in Part I, 8 in Part II)
  • Step-by-step CRA readiness path per product

02 · Discovery

SBOM and Vulnerability Management

No source code needed. You start from a firmware image, a build-time SBOM, your supplier's SBOM or an Excel/CSV component list. Components are matched against NVD, OSV, CVE Program records and vendor advisories (Espressif, Mbed TLS), and prioritised with CISA KEV and EPSS. ENISA EUVD is used for evidence of active exploitation and for source links. The sources are updated daily.

  • Firmware image analysis, including Intel HEX, S-record and ELF files (Linux ELFs, ESP32 and Arm Cortex-M ELF/AXF)
  • SBOM import: CycloneDX 1.4–1.7 (JSON, XML), SPDX 2.2–2.3 (JSON, tag-value) and SPDX 3.0.1 (JSON-LD)
  • Debian and Ubuntu LTS packages are matched with the distribution's own security data and source package name
  • Every finding links to its source record; records NVD has not yet processed are flagged for review
  • Internal records for vulnerabilities in your own code that have no CVE; an Article 14 notification can start from such a record
  • A form and inbox for vulnerability reports from outside
  • VEX in CSAF 2.0 and OpenVEX; your analyst makes the final call

03 · Reporting

CRA File and Reporting

The technical file and the EU declaration of conformity are prepared from the product's records. Article 14 notifications become drafts in the field order of the form of ENISA's Single Reporting Platform (SRP); you submit them in the ENISA portal.

  • Technical file (Annex VII) and EU declaration of conformity (Annex V and simplified Annex VI), as PDF and Word
  • Public, versioned user information page (Annex II)
  • SBOM output: CycloneDX 1.6, SPDX 2.3 and 3.0.1; BSI TR-03183-2 field report
  • Article 14: drafts in SRP field order, deadline tracking for 24 hours, 72 hours and the final report
  • Signed archive with RFC 3161 time stamps for submitted notifications
  • For non-EU manufacturers: authorised representative, importer and distributor records; a suggested coordinating CSIRT under Article 14(7)

04 · Device

Device Security and OTA

Optional. If you have a connected fleet, your devices send signed telemetry and receive signed updates: the device verifies the signature, writes the update to its A/B partition and returns to the previous version if the new one does not boot. The device's hardware security features are recorded as Annex I evidence; without a fleet they can also be declared manually.

  • Telemetry signed with each device's own key; tampering and memory corruption events
  • Critical device events automatically open an assessment record; your team decides whether they must be reported
  • Signed OTA: ECDSA P-256 signed manifest, anti-rollback protection, A/B partitions and return to the previous version after a failed boot
  • Hardware features such as secure boot recorded as Annex I evidence

Device SDK: ESP32 is ready; an NXP port is in development; STM32 and embedded Linux are on the roadmap. Tell us your board and we will adapt it together in the pilot programme.

Free tool

Check your SBOM for free

Drop your SBOM or lock file: see the component list, known vulnerabilities and a field-by-field quality report against the CRA and BSI TR-03183-2. The file is read inside your browser; only package name, version and ecosystem are sent out.

Supported files

Existing SBOM
CycloneDX 1.4–1.7 JSON and XML (bom.json, bom.xml, *.cdx.json), SPDX 2.2 / 2.3 JSON and tag-value (*.spdx.json, *.spdx), SPDX 3.0.1 JSON-LD
Embedded
Yocto *.manifest, Yocto license.manifest, Buildroot manifest.csv
JavaScript
package-lock.json, package.json, yarn.lock, pnpm-lock.yaml
Python
requirements.txt, Pipfile.lock, poetry.lock
Java, Rust, Go, PHP
pom.xml, Cargo.lock, go.mod, composer.lock
Open the scanner
Flow

What happens to a vulnerability

When a new CVE is published, this is what happens, in order.

  1. Match

    The CVE is matched to a component in your SBOM. You see which products and firmware versions contain it. Earlier SBOMs are re-checked as new vulnerability data arrives.

  2. Prioritise

    The CVE is checked against CISA's Known Exploited Vulnerabilities catalogue and EPSS. Known exploited ones move to the top of the list.

  3. Notify

    The legal deadline starts when you become aware of active exploitation. The platform records that moment, calculates the deadlines from it and prepares the report drafts. Your team reviews them and submits them in ENISA's portal.

  4. Patch

    The fixed version is signed and offered to the devices. Each device verifies the signature and version and reports the result. Every step is written to the audit trail.

Architecture

Security in three layers

A turtle shell has bone underneath and keratin plates on top. We built our architecture the same way, layer by layer from hardware to cloud.

Fig. 2 · Shell cross-section
CRA

The timeline is moving

The Regulation covers most manufacturers placing products with digital elements on the EU market. Reporting obligations have started. All essential requirements become mandatory on 11 December 2027.

 days · Until 11 December 2027

24 hours

Early warning deadline for an actively exploited vulnerability

10 years

Minimum retention for technical documentation

€15 million

or 2.5% of worldwide turnover. Maximum fine for breaching the essential requirements

FAQ

Common questions

No. Files are parsed in a Web Worker in your browser. If you leave the vulnerability check on, only package name, version and ecosystem are sent to OSV.dev; when there are findings, the CISA KEV list is downloaded from this site's server, and that request carries no data about your file. The file itself never leaves your computer.

It is not. The SBOM is one part of the vulnerability handling requirements in Annex I. The CRA also requires fixing vulnerabilities, reporting active exploitation, distributing updates securely and keeping technical documentation.

On 11 September 2026. When you become aware of an actively exploited vulnerability you have 24 hours for an early warning and 72 hours for the notification. The final report is due no later than 14 days after a fix is available.

No. The EN 18031 series was written for the cybersecurity requirements of the Radio Equipment Directive (RED). Separate harmonised standards are being prepared for the CRA. See the EN 18031 guide.

We are built for embedded hardware. We analyse the firmware image itself, not just source manifests; no source code is needed. Class and Annex I decisions, the SBOM, decisions on vulnerabilities, the technical file and Article 14 drafts come together in the same product record. The device side (C SDK, signed OTA) is optional.

Most products with digital elements are in the default category. Routers, modems, smart locks and security cameras are Class I. Our short class check shows the likely class; for examples by field, see our industry pages.

We start with a technical call, then run a free CRA pre-scan of a firmware you choose. After that we plan a pilot with scope and success criteria agreed in writing up front. See the pilot program.

Contact

Let's talk about your product

Tell us briefly about your product and how your devices connect. One of our engineers will read your message and get back to you.

The pilot program starts with a free CRA pre-scan of a firmware you choose. See how it works.

Your details are processed as described in our KVKK Notice.

Address
Teknopol Istanbul

Infrastructure

  • Powered by AWS Cloud Computing

© 2026 NVIDIA, the NVIDIA logo, and NVIDIA Inception are trademarks and/or registered trademarks of NVIDIA Corporation in the U.S. and other countries.

Amazon Web Services, AWS and the Powered by AWS logo are trademarks of Amazon.com, Inc. or its affiliates. Claude and Anthropic are trademarks of Anthropic PBC. Program memberships do not imply endorsement of TegmenSoft or its products by the respective companies.