Cyber Resilience Act · European Union

The Cyber Resilience Act, for people buying security software.

What the EU's Cyber Resilience Act requires of the companies that make software, when each part applies, and what to ask the vendor of the SIEM you run, which the CRA lists as an important product.

Buy nano
Talk to sales
What the CRA is

Security rules for the products themselves.

NIS2 and DORA regulate organizations that use technology. The CRA regulates the hardware and software products they buy, by putting obligations on whoever makes and sells them.

Scope · Art. 2–3

Products with digital elements.

Hardware and software products, and their remote data processing solutions, that connect to a device or network and are made available on the EU market. Components sold separately count too.

Regulation (EU) 2024/2847 ↗
Obligations · Art. 13–23

Manufacturers carry most of it.

Manufacturers meet the essential requirements in Annex I, handle vulnerabilities for the support period and report exploited vulnerabilities. Importers and distributors check that what they sell carries the CE marking and documentation.

Regulation (EU) 2024/2847 ↗
Outside scope · Art. 2, recital 12

Not pure SaaS, not every open-source project.

Medical devices, vehicles, certified aviation products, marine equipment and national-security products are excluded. Cloud services are covered only as part of a product; SaaS on its own falls under NIS2. Non-commercial open source is out.

Regulation (EU) 2024/2847 ↗
When it applies

Reporting is already live.

The CRA phases in over three years. The reporting duty came first, and it already covers products placed on the market before it applied.

  1. 10 Dec 2024 In effect

    CRA in force

    Published in the Official Journal on 20 November 2024; in force twenty days later (Art. 71(1)).

    EUR-Lex · CRA ↗
  2. 11 Jun 2026 In effect

    Conformity assessment bodies

    Chapter IV, on notifying conformity assessment bodies, applies (Art. 71(2)).

    EUR-Lex · CRA ↗
  3. 11 Sep 2026 In effect

    Reporting obligations apply

    Article 14 reporting of actively exploited vulnerabilities and severe incidents applies, including for products placed on the market earlier (Art. 69(3)).

    European Commission ↗
  4. 11 Dec 2027 Next

    Everything else applies

    Essential requirements, conformity assessment and CE marking for products placed on the market from this date (Art. 71(2)).

    EUR-Lex · CRA ↗
SIEMs under the CRA

Your SIEM is a Class I important product.

Annex III lists the product categories whose security matters most. SIEM systems are item 7 of Class I. The Commission's technical description makes clear which products that covers.

Implementing Regulation (EU) 2025/2392, Annex I, item 7
“Products with digital elements that collect data from multiple sources, analyse and correlate that data and present it as actionable information for security-related purposes, such as threat and incident detection, forensic analysis or compliance purposes.”
Implementing Regulation (EU) 2025/2392 ↗
Conformity · Art. 32(2)

Standards, or a third party.

From 11 December 2027 a Class I product can use the manufacturer's own assessment only where it fully applies harmonized standards, common specifications or a certification scheme at assurance level "substantial". Otherwise a notified body is involved.

Core functionality · Art. 7(1)

It's what the product is for.

A product is in the category when its core functionality is that of a SIEM. The Commission's example: a SOAR tool that can do SIEM-like work is not, by that alone, a SIEM.

For you, the buyer

Ask before December 2027.

A SIEM bought today may still be running after the full rules apply. Ask the vendor how it plans to meet the Class I assessment, and what happens to the version you run.

What manufacturers must do

The obligations, and what to ask.

The main manufacturer obligations, in plain English, with the question to put to your SIEM vendor in the last column. The answers show how seriously a vendor takes them.

Regulation (EU) 2024/2847: what manufacturers owe their customers

These obligations sit with the product's manufacturer. The last column is the evidence a SIEM vendor should be able to walk you through.

Ref The obligation In plain English What to ask your vendor
Art. 13(1), Annex I Part I Design, develop and produce products with digital elements in accordance with the essential cybersecurity requirements. EUR-Lex · CRA Secure by design and by default: no known exploitable vulnerabilities at release, secure default configuration, access control, data protection, minimal attack surface, logging of relevant internal activity.
Ask: how do you assess cybersecurity risk for the product, and which harmonized standard or other specification do you follow?
Art. 13(8) Handle vulnerabilities effectively for the support period, which shall be at least five years unless the product is expected to be in use for less. EUR-Lex · CRA Security updates for a defined, published period.
Ask: what is the support period for the version you are buying, and how are security updates delivered?
Annex I Part II(1) Identify and document vulnerabilities and components, including by drawing up a software bill of materials in a commonly used, machine-readable format covering at least the top-level dependencies. EUR-Lex · CRA An SBOM is mandatory for the manufacturer to keep. Publishing it to users is optional.
Ask: do you maintain an SBOM for each release, and will you share it with customers?
Annex I Part II(5)–(8) Have a coordinated vulnerability disclosure policy and a contact address for reporting vulnerabilities; distribute updates securely and without delay, free of charge. EUR-Lex · CRA A published way to report bugs, and signed, timely fixes.
Ask: where is your vulnerability disclosure policy, and how do I verify that an update came from you?
Art. 14 Notify actively exploited vulnerabilities and severe incidents affecting the product's security to the coordinating CSIRT and ENISA through the Single Reporting Platform. EUR-Lex · CRA Live since 11 September 2026, for products already on the market too.
Ask: how will you tell customers about an actively exploited vulnerability in the product, and how fast?
Article 14 reporting

The manufacturer's 24-hour clock.

Since 11 September 2026, manufacturers report actively exploited vulnerabilities and severe incidents through ENISA's Single Reporting Platform. If you make products with digital elements yourself, knowing quickly that one is being exploited depends on the telemetry you collect and search.

  1. 0 h

    Aware of an actively exploited vulnerability or severe incident

    The clock starts when the manufacturer becomes aware.

  2. 24 h

    Early warning

    Without undue delay, and within 24 hours of becoming aware of an actively exploited vulnerability or severe incident.

  3. 72 h

    Notification

    General information on the product, the exploit or incident, and corrective measures taken or that users can take.

  4. 14 days / 1 month

    Final report

    Vulnerability: within 14 days after a fix or mitigation is available. Severe incident: within one month of the 72-hour notification.

Regulation (EU) 2024/2847, Article 14(2) and (4). Reports go via ENISA's Single Reporting Platform to the coordinating CSIRT.
nano and the CRA

Where nano stands today.

nano, LLC makes nano, software customers install in their own environment, including in the EU. Under the CRA that makes nano a manufacturer of a SIEM. Here is what is in place.

Vulnerability reports

A security contact and a 90-day window.

Report a vulnerability in nano to security@nano.rs. The SECURITY.md in the open-source repository describes the process, and a PGP key is available on request. nano follows coordinated disclosure with a 90-day window.

Fixes and updates

Published advisories, signed releases.

Fixes are published as GitHub Security Advisories on the open-source repository; two were published in September and October 2026. Releases ship as signed bundles: the documented install steps verify the signature, the upgrade command checks it before anything changes, and images are pinned by digest. Air-gapped installs verify signed offline bundles the same way. Air-gapped deployment

Transparency

An open-source core and an SBOM per release.

nano's core engine is published under AGPL-3.0, so you can read the code that runs in your environment. Every release ships a CycloneDX SBOM, for the release and for each image. The open-source SBOMs are public on the GitHub release; Self-run customers can request the SBOM for the commercial modules. Open source

FAQ

Questions we get asked.

What is the Cyber Resilience Act?

The Cyber Resilience Act (CRA) is Regulation (EU) 2024/2847. It sets cybersecurity requirements for products with digital elements, meaning hardware and software products and their remote data processing solutions, placed on the EU market. Manufacturers must design products to meet essential cybersecurity requirements, handle vulnerabilities for a support period, report actively exploited vulnerabilities and severe incidents, and affix the CE marking once the full rules apply.

When does the Cyber Resilience Act apply?

The CRA entered into force on 10 December 2024. The reporting obligations in Article 14 have applied since 11 September 2026, including for products placed on the market before then. The rules on conformity assessment bodies applied from 11 June 2026. The remaining obligations, including the essential requirements and CE marking, apply from 11 December 2027.

Who does the CRA apply to?

Manufacturers of products with digital elements made available on the EU market, plus importers and distributors, each with their own obligations. A manufacturer outside the EU, such as a US software company, is covered when its product is made available in the EU. Open-source software stewards have a lighter set of obligations under Article 24.

What are the exceptions? Does the CRA cover SaaS or open-source software?

The CRA does not apply to products covered by the EU rules on medical devices, in vitro diagnostics, motor vehicles and certified aviation products, to marine equipment, to products developed exclusively for national security or defense, or to identical spare parts (Article 2). Pure SaaS is generally outside the CRA: cloud services are covered only as remote data processing solutions of a product, and recital 12 notes that NIS2 covers cloud services such as SaaS. Free and open-source software is covered only when made available in the course of a commercial activity (recital 18); open-source software stewards have lighter duties under Article 24.

Is an SBOM mandatory under the CRA?

Yes, for manufacturers. Annex I Part II(1) requires them to draw up a software bill of materials in a commonly used, machine-readable format covering at least the top-level dependencies of the product. It forms part of the technical documentation, and a market surveillance authority can request it. Manufacturers are not required to publish it; if they choose to make it available to users, the user information must say where.

What must manufacturers report under the CRA, and how fast?

Under Article 14, an actively exploited vulnerability or a severe incident affecting the security of the product: an early warning within 24 hours of becoming aware, a notification within 72 hours, and a final report within 14 days after a fix is available (vulnerabilities) or within one month of the notification (severe incidents). Reports go through ENISA's Single Reporting Platform to the CSIRT designated as coordinator, and ENISA receives them at the same time.

Is a SIEM an important product under the CRA?

Yes. Security information and event management (SIEM) systems are listed in Annex III, Class I, of the CRA. Implementing Regulation (EU) 2025/2392 describes them as products that collect data from multiple sources, analyze and correlate it, and present it as actionable information for security purposes such as threat and incident detection, forensic analysis or compliance. Class I products need either the manufacturer's own assessment against harmonized standards, common specifications or a suitable certification scheme, or a third-party conformity assessment, from 11 December 2027.

What should you ask your SIEM vendor about the CRA?

Ask how the vendor plans to meet the Class I conformity assessment for its SIEM by December 2027, what the support period is, whether it keeps an SBOM per release and will share it, where its vulnerability disclosure policy and security contact are, how updates are signed and delivered, and how it will tell you about actively exploited vulnerabilities. For hosted SIEMs, also ask which parts are the product and which are a service, because the service side falls under NIS2 rather than the CRA.

How is nano approaching the CRA?

nano, LLC is the manufacturer of nano, software it makes available to customers in the EU. nano does not claim CRA conformity for any product today. What is in place now: vulnerability reports go to security@nano.rs, under the process in SECURITY.md in the open-source repository, with coordinated disclosure and a 90-day window. Fixes are published as GitHub Security Advisories on the open-source repository; two were published in September and October 2026. Releases are signed, their signatures are verified before install and upgrade, and images are pinned by digest. Every release ships a CycloneDX SBOM, one for the release and one per image, also attached to each image as an attestation. The open-source SBOMs are public on each GitHub release, and Self-run customers can request the SBOM for the commercial modules. The core is open source, so you can inspect it.

Primary sources

Read the rules yourself.

Start with nano.

From US$149/month at 5 GB/day, US$279/month at 10 GB/day (list price, billed monthly; 10% off billed annually). Every feature in one license, and one license covers two installs.

Buy nano
Talk to sales