CRA REPORTING · ART. 14 REGULATION (EU) 2024/2847

CRA vulnerability reporting: ready for the 24-hour deadline in 10 days

Since 11 September 2026 the CRA requires manufacturers to report actively exploited vulnerabilities via ENISA within 24 hours, even for products already sold. You get 30 days of CVE watch on your SBOM free; we make you reporting-ready in 10 days from €3,900 excl. VAT.

Start 30 days of free CVE watchYour SBOM is enough · ends automatically, no subscription
Quick and free:CRA product check

The clock starts when you know. The early warning is due 24 hours after you become aware of exploitation. Without an SBOM you often never learn that an affected library is in your product.

ReferencesT-Systems · Olingo Medical · Lumii · Rowan Legal

Leave your number, I'll call you

Krystof Olik · founder and CEO

Same working day (CET), otherwise the next working morning.

Or email me directly at info@ollsoft.ai

We use your details only for this request. Privacy
Applies since
11 Sep 2026 (Art. 71(2))
Early warning
within 24 hours of awareness (Art. 14(2) and (4))
Notification
within 72 hours of awareness
Final report
14 days after a corrective or mitigating measure is available; for incidents 1 month after the notification

CRA updates by email. Once a month: what changed and what it means for your product.

PricingCVE watch: freeReporting setup: from €3,900Operation: from €390 per monthFull offer

Why Ollsoft?

The CVE watch runs on our own tool and framework for CRA testing, not as a one-off audit.

  • it re-checks the SBOM and vulnerabilities on every release
  • when a new exploited vulnerability appears, we tell you what has to be done, or take care of it for you
  • an AI agent triages every match, an engineer decides, and the decision is recorded as OpenVEX
  • we do the technical work and prepare processes and documentation; lawyers at our partner firm Rowan Legal validate them and prepare the contracts
Two Ollsoft engineers at a laptop, code on a monitor beside them

What exactly must I report?

CRA vulnerability reporting (Art. 14 of Regulation (EU) 2024/2847) obliges manufacturers, since 11 September 2026, to report actively exploited vulnerabilities in their product and severe incidents affecting its security via the ENISA platform (Art. 14(1) and (3)).

  • “actively exploited”: there is reliable evidence that a malicious actor exploited it in a system without the owner’s permission (Art. 3(42))
  • an incident is severe if it affects, or can affect, the protection of sensitive or important data or functions, or can bring malicious code into your product or your users’ systems (Art. 14(5))
  • a vulnerability in a third-party component is reportable only once exploited in your product (Commission guidance, para 218)
  • if the vulnerable code is not reachable in your product, there is no reporting obligation
  • you may still report voluntarily (Art. 15)

When does the 24-hour clock start?

When, after an initial assessment, you have a reasonable degree of certainty that a vulnerability in your product is being exploited or that a severe incident occurred (Commission guidance, para 213).

  • the assessment must start as soon as a signal arrives (paras 213 and 214)
  • exploitation you already knew about before 11 September 2026 is not reportable retroactively (para 217)
  • if an older vulnerability is exploited, or you learn of it, only after that date, the clock applies

How does reporting via the ENISA platform work?

Via ENISA’s Single Reporting Platform, simultaneously to the CSIRT designated as coordinator in the Member State of your main establishment and to ENISA (Art. 14(7)).

  • your main establishment is where your products’ cybersecurity decisions are predominantly taken
  • access only with EU Login and multi-factor authentication; create the account in advance
  • one primary and up to 20 secondary representatives per manufacturer
  • ENISA advises registering on the platform only when you need to report; with an EU Login account ready it takes minutes
  • English-only web interface, no API at launch
  • once aware of the exploitation or incident, also inform affected users, machine-readable where appropriate (Art. 14(8))

Why does reporting need an SBOM and CVE monitoring?

You can only report what you notice, and an SBOM lists the components and versions in each shipped product.

  • matched daily against vulnerability databases, it reveals a new case even when your code has not changed
  • exploited lists (CISA KEV, ENISA EUVD) show what attackers already use
  • triage then decides whether the vulnerable code is present, reachable and attacker-controllable
  • the verdict is recorded as OpenVEX, which documents your decision and answers customer questions

OFFER

From 30 free days to operation

The free watch runs on your SBOM, with no code access, and shows at once which components have vulnerabilities and which of them matter.

Step 1 · Start here

CVE watch, 30 days free

For 30 days you see every new vulnerability in one product and whether it may become reportable.

Free

What you get

  • you send us the SBOM of one product in a machine-readable format; no code access
  • daily matching against vulnerability databases, CISA KEV and ENISA EUVD
  • for every new match, whether it may become reportable: an AI agent proposes, an engineer decides
  • e-mail alert on actively exploited vulnerabilities
  • ends automatically, no subscription
Start 30 days of free CVE watch

Step 2

CRA reporting-ready in 10 days

You recognize reportable cases and can notify within 24 hours.

from €3,900excl. VAT, one-off

What you get

  • detailed review of code and infrastructure: SBOM from all repositories and reachability of vulnerabilities in the code
  • SBOM for every shipped product, generated in CI
  • CVE watch with triage for all products
  • reporting runbook: who assesses, who reports, who stands in
  • templates for early warning, 72-hour notification and final report
  • EU Login accounts with MFA prepared, competent CSIRT identified
  • user notification template (Art. 14(8))
  • one exercise with a simulated case
Request a quote

Step 3

CVE watch in operation

New vulnerabilities are triaged continuously and reports are prepared.

from €390 per monthexcl. VAT

What you get

  • daily matching for all products
  • triage and OpenVEX for every match
  • help filling in every report
  • VEX documents for your customers
Request a quote

GUARANTEE

10 days, or we keep working for free

If your reporting process is not operational 10 days after repository access, we keep working at no extra cost until it is. Applies to "CRA reporting-ready in 10 days".

Start 30 days of free CVE watch

Your SBOM is enough · ends automatically, no subscription

Leave your number, I'll call you

Krystof Olik · founder and CEO

Same working day (CET), otherwise the next working morning.

Or email me directly at info@ollsoft.ai

We use your details only for this request. Privacy

PROCESS

How it works

  1. 01

    A short call

    Products, SBOM, who handles security reports today. No code access.

  2. 02

    CVE watch from day 1

    On your SBOM, daily matching, free for 30 days.

  3. 03

    Reporting-ready in 10 days

    Code review, SBOM in CI, runbook, templates, accounts, exercise.

  4. 04

    Operation

    Triage of every match, help with every report.

REFERENCES

References and partners

T-Systems

We built the CRA compliance platform for T-Systems: it matches every product’s SBOM daily against new vulnerabilities and every six hours against exploited lists. An AI agent triages each new match and records the verdict as OpenVEX; a shipped, actively exploited component raises the Art. 14 steps with their 24-hour, 72-hour and 14-day deadlines.

Olingo Medical

AI for clinical documentation: more than 10 hospitals and clinics use it; in two university hospitals it runs entirely inside the hospital network. We prepared it for the CRA.

olingomedical.com

Lumii

A European AI toy that children talk to. We prepared it for the CRA.

lumiitoy.com

Rowan Legal

Our partner law firm for NIS2 and CRA: we do the technical work and prepare processes and documentation, its lawyers validate them and prepare the contracts. We also built AI for the firm that runs on its own servers, with no external APIs.

rowan.legal

CONTACT

Start with the free CVE watch

After a short call you send us the SBOM of one product and we switch on 30 days of CVE watch for free, with no code access. Then it ends on its own: no subscription, nothing to cancel.

Leave your number, I'll call you

Krystof Olik · founder and CEO

Same working day (CET), otherwise the next working morning.

Or email me directly at info@ollsoft.ai

We use your details only for this request. Privacy

FAQ

What clients ask us

Yes. Art. 69(3) extends it to all in-scope products placed on the market before 11 December 2027, and per the Commission guidance it continues after the support period ends.

The free watch runs on an SBOM you send us; we need no code access. If you have none, the 10-day package builds it from your repositories and hooks its generation into your release process.

You, as the manufacturer (Art. 14(1)). We set up the SBOM, monitoring, runbook and templates and help fill in every report. Legal review stays with your counsel, or lawyers at our partner firm Rowan Legal can do it.

Manufacturers that ship open source in their products report for those products now. Open-source stewards report from 11 December 2027, to the extent they are involved in development (Art. 24(3) and Art. 71(2)).

Infringements of Art. 14 can be fined up to €15m or 2.5% of worldwide annual turnover, whichever is higher (Art. 64(2)).

The first 30 days of CVE watch are free, on your SBOM and without code access. The 10-day package starts at €3,900 excl. VAT, ongoing CVE watch at €390 per month.

"CRA reporting-ready in 10 days" (from €3,900) covers only the reporting that already applies: SBOM in CI, CVE watch, runbook, templates, EU Login accounts and an exercise. "CRA readiness in 6 weeks" (from €7,900) prepares the whole product for 11 December 2027 and includes the ENISA reporting runbook too. In operation, both "CVE watch in operation" (from €390 a month) and "CRA in operation" (from €590 a month) match daily against new CVEs, triage matches as OpenVEX and help with reports; "CRA in operation" also generates the SBOM on every release and updates the risk assessment and documentation. All prices excl. VAT.

Newsletter

CRA updates by email

The CRA keeps being filled in: Commission guidance, the ENISA platform, harmonised standards. Once a month, and whenever something important changes, we send a short overview of what changed and what it means for your product.