Cyber Resilience Act: can you still sell your products in the EU after 11 December 2027?

Be ready now to report an actively exploited vulnerability or severe incident in any product on the EU market within 24 hours. Before 11 December 2027, give every product a class, a support period, a risk assessment, an SBOM and technical documentation, so it can carry the CE marking.

Reviewed
Next review
Version
1.0
Written for
Companies that make, import or distribute hardware or software sold in the EU, and open-source stewards

If you only do five things

  1. Be able to report within 24 hours.

    Reporting has applied since 11 September 2026, also to products placed on the market before December 2027 and after their support ends3. Name an owner and a deputy with EU Login accounts and MFA, and decide which CSIRT you report to5.

  2. Classify each product by its core functionality.

    Match it against Implementing Regulation (EU) 2025/23924. Default products may always self-assess; important and critical ones may need a notified body3.

  3. Set a support period per product.

    Base it on expected use, comparable products and your components' own support, and make it at least 5 years unless use is shorter1. Show the end month and year at purchase1.

  4. Write the risk assessment first.

    It decides how each Annex I requirement applies and goes into the technical documentation1. Cover planned features too, so the updates that add them aren't substantial modifications3.

  5. Run vulnerability handling as a process.

    Due diligence on third-party and open-source components, an SBOM per release, a disclosure policy and contact, and free security updates1. The supply chain and secure development sheets show how.

Are you in scope, and in which role?

  1. Does it connect to a device or network?

    If so, the CRA covers it, with the remote data processing it needs to work1. Web apps used only in a browser, websites and SaaS are not products themselves3.

  2. Is it excluded?

    Yes, if it's a medical or diagnostic device, a motor vehicle, a certified aviation product, marine equipment, an identical spare part or made only for national security or defense1.

  3. Do you supply it commercially?

    Charging for it or for support beyond cost, monetizing it through other services or requiring personal data for more than security and compatibility counts, even if it's free1. Open source you don't monetize doesn't1.

  4. Are you an open-source steward?

    You are if you're a foundation or company that systematically supports non-monetized open source meant for commercial use3. Stewards need a documented security policy1, report from December 20275 and can't be fined1.

  5. Which role do you have?

    Manufacturers sell under their own name; importers and distributors check the CE marking and documents first1. Rebranding or substantially modifying a product makes you its manufacturer1.

Product classes and conformity assessment

  • Default. Anything whose core functionality isn't in Annex III or IV. Self-assessment (module A) is always allowed3.
  • Important, class I. 19 categories, such as identity and access management, browsers, password managers, antivirus, VPNs, operating systems, routers and smart home security products. Self-assess only by fully applying a cited harmonized standard, common specification or EU certificate at level substantial; otherwise use a notified body1.
  • Important, class II. Hypervisors, container runtimes, firewalls, intrusion detection and prevention systems and tamper-resistant chips. Always third party1.
  • Critical. Hardware security boxes, smart meter gateways and smartcards: EU certification where a delegated act requires it, otherwise as class II1. The class of the whole product counts, not that of its components3.
  • Check which standards are cited. Only standards cited in the Official Journal give presumption of conformity1. ETSI's approval of its 17 product-specific drafts ends between mid-September and mid-November 2026, by product10.

Annex I in practice

  • No known exploitable flaws at release. Known means in the EU vulnerability database or another prominent one, or reported to you3.
  • Secure defaults. A secure default configuration with a reset, access control, encryption of stored and transmitted data, minimal data and a way to delete it all1.
  • Automatic security updates on by default, where applicable. With an opt-out, notifications and a way to postpone. Not required for components or where users don't expect them, as in industrial networks1.
  • An SBOM per release. Machine-readable, covering at least top-level dependencies, and it needn't be public1. BSI TR-03183-2 asks for CycloneDX 1.6 or SPDX 3.0.1 or later, with dependencies resolved through everything you ship8.
  • One contact point, not just a chatbot. A single point of contact not limited to automated tools, plus a disclosure policy1. BSI's voluntary TR-03183-3 adds a signed security.txt9.
  • Free fixes, kept available. Keep each security update available for 10 years or the rest of the support period, if longer1. For software, fixing only the latest version is fine if upgrading costs users nothing extra1.
  • Advisories and upstream reports. Publish fixed flaws, in CSAF as the BSI recommends19, and send component flaws to their maintainer1.

Reporting clocks since 11 September 2026

Clocks start at reasonable certainty after a prompt first check3. Report once on ENISA's platform, in Germany to CERT-Bund, and tell affected users16.

Actively exploited vulnerability

Reliable evidence of exploitation1; a public exploit isn't enough6.

  1. 24 hoursEarly warning
  2. 72 hoursNotification
  3. Fix + 14 daysFinal report

Severe incident

It harms or could harm the product's protection of sensitive or important data or functions, or could plant malicious code in it or users' systems1. Ransomware at the maker counts only if it could affect the product, its updates or signing keys6.

  1. 24 hoursEarly warning
  2. 72 hoursNotification
  3. 1 month laterFinal report

Documentation, CE marking and fines

  • Technical documentation (Annex VII). Architecture, vulnerability handling with SBOM and disclosure policy, risk assessment, support period reasons, standards, test reports and the declaration. Keep it 10 years or for the support period, if longer1.
  • EU declaration of conformity. Follow Annex V, ship it or a simplified version with its web address, and issue one for all EU acts that need one1.
  • CE marking from 11 December 2027. On the product, or the packaging and declaration; for software, on the declaration or its website1.
  • Fines up to €15 million or 2.5% of worldwide turnover. For breaching Annex I or Articles 13 and 14; €10 million or 2% for most other duties. Micro and small manufacturers aren't fined for a late 24-hour early warning, under Article 64(10) as corrected in July 202512.

What you can skip

  • Waiting for harmonized standards. The risk assessment, SBOM, disclosure policy and update channel don't depend on them.
  • Reporting every vulnerable dependency. Flaws that aren't reachable or exploited in your product aren't reportable; tell the maintainer3.
  • Redesigning products that already hold up. Designs from before the CRA need no change if the risk assessment shows adequate measures3.
  • Registering on ENISA's platform early. ENISA advises registering only when you first need to report5.

Mistakes that cost the most

  • Counting on the transition for hardware. Every unit placed on the market from 11 December 2027 must comply, even of an older model3.
  • Picking the wrong CSIRT. The notification may be invalidated and need resubmitting5.
  • Rebranding without noticing. An importer or distributor selling under its own name becomes the manufacturer1.
  • A 5-year support period by reflex. The Commission says 5 years is not a default; products used longer need longer support3.

What changed in 2026

  • Reporting went live on 11 September. ENISA's platform is English only, has no API yet, and its 72-hour counter can show reports overdue early5.
  • Draft Commission guidance, 27 July. It explains scope, open source, substantial modification and support periods, and isn't binding3.
  • Germany is naming the BSI. A bill the Bundestag passed on 15 October would make it market surveillance authority1112.
  • Radio equipment moves to the CRA. The radio equipment cybersecurity delegated act is repealed from 11 December 202713.

What this looks like at your size

Small team, no security staff

  • List every product and version you sell in the EU, with its class and support end date.
  • Write a one-page runbook: who reports, to which CSIRT, from which EU Login accounts.
  • Work through BSI TR-03183-1 as a checklist7.

Growing, with IT or security staff

  • Name a product security owner and ship an SBOM and advisories with every release.
  • Plan for a notified body now if a product needs one; Member States aim to have enough by 11 December 20261.
  • Document one product end to end, then reuse it for its variants3.

Enterprise or regulated

  • Build module H on your ISO/IEC 27001 ISMS, as BSI TR-03183-H shows7.
  • Run CRA reports in your NIS2 incident process; the EU security laws sheet has those clocks.
  • Agree how importers and distributors pass on the vulnerabilities they must report to you1.