CRA. Cyber Resilience Act: Obligations, Deadlines and Reporting

Regulation (EU) 2024/2847 on horizontal cybersecurity requirements for products with digital elements (Cyber Resilience Act)

In force EU-wide
StatusIn forceApplies since 10/12/2024
Legal actEU Regulationdirectly applicable
Fines up to2.5%details below

Overview

The Cyber Resilience Act (CRA, Regulation (EU) 2024/2847) sets the first mandatory cybersecurity requirements for all products with digital elements – hardware and software that can be connected directly or indirectly to a device or network. Manufacturers must ensure security throughout the product lifecycle: from design and distribution to the end of the support period.

The regulation entered into force on 10 December 2024 and applies in stages. Since 11 September 2026, manufacturers have had to report actively exploited vulnerabilities and severe incidents. From 11 December 2027, products may only be placed on the market with CE marking under the CRA.

Timeline

DateWhat applies
10.12.2024Entry into force
11.06.2026Rules on conformity assessment bodies (Chapter IV) apply
11.09.2026Reporting obligations under Article 14 apply – including for products already on the market
11.12.2027Full application: essential requirements, conformity assessment, CE marking

Products placed on the market before 11 December 2027 only fall under the other requirements if they are substantially modified from that date. The reporting obligations, by contrast, already apply to the entire installed base.

Who Is Affected?

The CRA covers the entire digital product supply chain:

  • Manufacturers of hardware and software with digital elements – including those outside the EU
  • Authorised representatives and importers placing such products on the EU market
  • Distributors, who must check that CE marking and documentation are in place
  • Open-source software stewards, who are subject to a lighter regime

Products already covered by sectoral rules are excluded – such as medical devices, in vitro diagnostics, motor vehicles, aviation and marine equipment – as are products developed exclusively for national security or defence. Free and open-source software that is not supplied in the course of a commercial activity is also outside the scope.

Product Classes and Conformity Assessment

CategoryExamplesConformity assessment
Default productsmost products with digital elementsinternal control by the manufacturer (self-assessment)
Important products, class I (Annex III)e.g. password managers, VPNs, browsers, operating systems, routers and switches, smart home security productsself-assessment only if harmonised standards, common specifications or a certification scheme are applied; otherwise third-party assessment by a notified body
Important products, class II (Annex III)e.g. hypervisors and container runtime systems, firewalls, intrusion detection and prevention systems, tamper-resistant microprocessorsalways third-party assessment by a notified body
Critical products (Annex IV)e.g. smart meter gateways, smartcards and secure elementsEuropean cybersecurity certification where required; otherwise as class II

Core Obligations for Manufacturers

  1. Security by design and by default: Meet the essential cybersecurity requirements in Annex I, e.g. secure default configuration, protection against unauthorised access, data minimisation
  2. Risk assessment: A documented cybersecurity risk assessment as part of the technical documentation
  3. Vulnerability handling: Processes for identifying, documenting and remediating vulnerabilities, including a coordinated vulnerability disclosure policy
  4. Software Bill of Materials (SBOM): Documentation of software components, at least the top-level dependencies
  5. Security updates: Free of charge for the entire support period – as a rule at least five years; each update remains available for at least ten years
  6. Conformity assessment and CE marking from 11 December 2027, including an EU declaration of conformity
  7. Reporting obligations since 11 September 2026

Reporting Obligations Since 11 September 2026

Manufacturers must report actively exploited vulnerabilities and severe incidents affecting the security of their product via ENISA’s single reporting platform. The report goes to the CSIRT designated as coordinator in the Member State of the main establishment; ENISA receives it at the same time.

StepActively exploited vulnerabilitySevere incident
Early warningwithin 24 hourswithin 24 hours
Notificationwithin 72 hourswithin 72 hours
Final reportno later than 14 days after a fix is availablewithin one month of the notification

Manufacturers must also inform affected users about the incident and possible mitigation measures. The reporting obligations apply to all products in scope, including those placed on the market before 11 December 2027.

Companies that are also subject to the NIS2 Directive must serve both reporting channels in parallel: NIS2 covers incidents in their own operations, the CRA covers vulnerabilities and incidents in their products.

Fines

InfringementMaximum fine
Essential cybersecurity requirements (Annex I) and manufacturer obligations under Articles 13 and 14EUR 15 million or 2.5% of global annual turnover
Other obligations under the regulationEUR 10 million or 2% of global annual turnover
Incorrect, incomplete or misleading information to notified bodies or authoritiesEUR 5 million or 1% of global annual turnover

The higher amount applies in each case. Micro and small enterprises are not fined for missing the 24-hour early warning deadline, and open-source software stewards are not fined at all. Market surveillance authorities can also order products to be withdrawn or recalled.

National Implementation

As an EU regulation, the CRA applies directly. Member states must, however, designate market surveillance authorities and notifying authorities and lay down penalties.

CountryStatus (October 2026)
GermanyOn 15 October 2026 the Bundestag adopted the act implementing the Cyber Resilience Act. It designates the BSI as market surveillance authority and notifying authority. The act has not yet been promulgated.
AustriaThe notifying authority sits within the Federal Chancellery. The market surveillance authority has not yet been designated.
SwitzerlandThe CRA does not apply. Swiss manufacturers supplying the EU must, however, meet its requirements for those products.
  • NIS2 Directive – cybersecurity obligations for operators and service providers
  • Product Liability Directive – software counts as a product; missing security updates can constitute a defect
  • GPSR – general product safety for consumer products
  • AI Act – high-risk AI systems that meet the CRA are deemed compliant with its cybersecurity requirements

CRA: Does it affect you?

Find out if and how this regulation affects your company – we're happy to advise you.

Frequently Asked Questions

Who is affected by the Cyber Resilience Act?

Manufacturers, authorised representatives, importers and distributors of products with digital elements made available on the EU market – from IoT devices and routers to operating systems, apps and industrial controls. The main addressee is the manufacturer, even if it is based outside the EU.

When does the CRA apply?

The CRA entered into force on 10 December 2024. The rules on conformity assessment bodies have applied since 11 June 2026 and the reporting obligations under Article 14 since 11 September 2026. All other obligations – in particular the essential cybersecurity requirements and CE marking – apply from 11 December 2027.

Does the reporting obligation also cover products already on the market?

Yes. Since 11 September 2026, the reporting obligations under Article 14 apply to all products in scope, including those placed on the market before 11 December 2027. The other requirements only apply to such legacy products if they are substantially modified from that date.

What must be reported, and by when?

Actively exploited vulnerabilities and severe incidents: early warning within 24 hours, notification within 72 hours, and a final report no later than 14 days after a fix is available (vulnerabilities) or within one month (incidents). Reports go through ENISA's single reporting platform to the competent CSIRT, with ENISA receiving them at the same time.

How long must security updates be provided?

For the entire support period, which as a rule is at least five years – shorter only if the product is expected to be used for less time. Each security update must remain available for at least ten years after release or for the rest of the support period, whichever is longer.

What fines apply?

Up to EUR 15 million or 2.5% of global annual turnover for breaches of the essential requirements, up to EUR 10 million or 2% for other breaches, and up to EUR 5 million or 1% for incorrect or incomplete information supplied to authorities – whichever amount is higher in each case.

Does the CRA apply in Switzerland?

No. However, Swiss manufacturers supplying products with digital elements to the EU must fully meet its requirements for those products – including the reporting obligations in force since 11 September 2026.