Guide Compliance Cybersecurity

Cyber Resilience Act (CRA): obligations for manufacturers, importers and distributors

The EU Cyber Resilience Act (Regulation (EU) 2024/2847) sets cybersecurity requirements for hardware and software products with digital elements sold in the EU. Reporting of actively exploited vulnerabilities and severe incidents has applied since 11 September 2026, and most other obligations apply from 11 December 2027. This guide covers who is in scope, how products are classified, what manufacturers, importers and distributors must do, and the evidence to prepare.

12 June 2026
Updated 18 November 2026
15 min read
Key takeaways
  • The Cyber Resilience Act (Regulation (EU) 2024/2847) covers hardware and software products with digital elements made available on the EU market, plus the remote data processing they need to perform their functions
  • Manufacturers carry most of the obligations. Importers and distributors have their own checking, cooperation and corrective duties, and become manufacturers if they rebrand or substantially modify a product
  • Products are default, important (Class I or Class II, Annex III) or critical (Annex IV). The category decides the conformity assessment route under Article 32
  • Since 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe incidents through the single reporting platform, under two separate sets of deadlines
  • The support period must be at least five years unless the product is expected to be in use for less time (Article 13(8))
  • Most other obligations apply from 11 December 2027

What the Cyber Resilience Act covers

The Cyber Resilience Act (CRA) sets cybersecurity requirements for products with digital elements sold in the EU. It entered into force on 10 December 2024. Before it, EU product law had no general rule that connected products be designed securely or patched after sale. From 11 December 2027, a manufacturer that places such a product on the EU market without meeting the essential requirements, or without handling its vulnerabilities over the support period, can face fines, withdrawal orders and recalls.

A product with digital elements is any software or hardware product, including its remote data processing solutions, whose intended or reasonably foreseeable use includes a direct or indirect data connection to a device or network. That covers smart home devices, routers, industrial controllers, operating systems, desktop and mobile apps, password managers and development tools when they are supplied in the course of a commercial activity. Products already covered by sector rules, such as medical devices, motor vehicles, civil aviation and marine equipment, are excluded or partly excluded (Article 2).

Software as a service is a common source of confusion. The CRA does not regulate SaaS as such. A cloud service that runs entirely on the provider's infrastructure and is not part of a product falls outside it, and may instead fall under NIS2. The Act does cover remote data processing solutions: processing at a distance that the manufacturer designs or controls and without which the product could not perform one of its functions (Articles 3(2) and 6). The cloud back end of a smart camera or the licence and sync service of an installed application can be in scope as part of that product.

For UK businesses

The CRA is EU law and does not apply to products sold only in Great Britain, where the Product Security and Telecommunications Infrastructure Act 2022 sets baseline rules for consumer connectable products. If you sell software or connected hardware to customers in the EU, the CRA applies to those products wherever your business is based.

Manufacturers, importers and distributors

Manufacturers develop or manufacture a product with digital elements, or have it designed or made, and market it under their own name or trademark. They meet the essential requirements, run vulnerability handling, carry out the conformity assessment, draw up technical documentation and the EU declaration of conformity, affix the CE marking and report under Article 14.

Importers place on the EU market products from a manufacturer established outside the EU (Article 19). Before placing a product on the market, an importer checks that:

  • the manufacturer has carried out the right conformity assessment and drawn up the technical documentation;
  • the product carries the CE marking and comes with the EU declaration of conformity (or a simplified version) and the required user information;
  • the manufacturer has identified a single point of contact for vulnerabilities and has vulnerability handling processes in place.

If an importer has reason to believe a product does not conform, it must not place it on the market until it does. If the product presents a significant cybersecurity risk, the importer informs the manufacturer and the market surveillance authorities. After placing the product, importers keep a copy of the declaration and the technical documentation available, tell the manufacturer about vulnerabilities they learn of, take corrective action when needed and cooperate with authorities.

Distributors make products available without being the manufacturer or importer (Article 20). They act with due care: they check the CE marking, the accompanying information and that the manufacturer and importer have met their identification duties. They must not supply a product they consider non-conforming. When they learn of non-conformity or a vulnerability, they inform the manufacturer, take corrective measures within their control and cooperate with market surveillance authorities.

When an importer or distributor becomes the manufacturer

An importer or distributor that places a product on the market under its own name or trademark, or carries out a substantial modification of a product already on the market, is treated as the manufacturer (Article 21). Any other person who substantially modifies a product becomes the manufacturer for the modified part (Article 22). This catches white-label hardware and OEM software arrangements.

Product categories and conformity assessment

The essential requirements are the same for every product. What changes with the category is how conformity must be demonstrated (Article 32). Important products are listed in Annex III, split into Class I and Class II. Critical products are listed in Annex IV. Annex I is not a list of products: it holds the essential requirements themselves.

CategoryWhere it is listedExamples from the annexesConformity assessment route
DefaultNot listed in Annex III or IVMost products, for example many business applications and consumer devices without a listed core functionInternal control (module A) is allowed. The manufacturer may also use a third-party route
Important, Class IAnnex III, Class IIdentity management systems, standalone browsers, password managers, anti-malware software, VPN products, SIEM, operating systems, routers and modems, smart home security productsInternal control only if harmonised standards, common specifications or a European cybersecurity certification scheme are applied in full. Otherwise EU-type examination (modules B and C) or full quality assurance (module H)
Important, Class IIAnnex III, Class IIHypervisors and container runtime systems, firewalls, intrusion detection and prevention systems, tamper-resistant microprocessors and microcontrollersEU-type examination (modules B and C), full quality assurance (module H), or a European cybersecurity certification scheme at assurance level at least "substantial"
CriticalAnnex IVHardware devices with security boxes, smart meter gateways, smartcards and secure elementsEuropean cybersecurity certification where the Commission requires it by delegated act. Until then, the Class II routes apply

Classification depends on the product's core functionality, not its trade name or the sector you sell into. A product that merely integrates a listed component, such as a smart fridge with a browser built in, is not an important product for that reason alone. A product whose core function is a listed one, such as a standalone password manager, is. The Commission's implementing regulation on the technical descriptions of Annex III and IV categories sets out where each category starts and ends, and it is worth reading before you settle on a class.

The essential cybersecurity requirements

Annex I has two parts. Part I covers the properties of the product. Part II covers the vulnerability handling the manufacturer must run for as long as the product is supported.

Part I: product properties

  • Products are designed, developed and produced to ensure a level of cybersecurity appropriate to the risks, based on a documented cybersecurity risk assessment (Article 13(2)).
  • They are made available without known exploitable vulnerabilities.
  • They ship with a secure by default configuration, with the option to reset to the original state.
  • Vulnerabilities can be addressed through security updates, including automatic updates where applicable, with an opt-out.
  • They protect the confidentiality, integrity and availability of data, process only the data needed for the intended purpose, limit attack surfaces and reduce the impact of incidents.
  • They record and monitor relevant internal activity, and let users remove their data and settings securely.

Part II: vulnerability handling

  • Identify and document vulnerabilities and components, including an SBOM.
  • Address and remediate vulnerabilities without delay, and provide security updates, where technically feasible separately from functionality updates.
  • Test and review the product's security regularly.
  • Publish information about fixed vulnerabilities once an update is available, with limited exceptions.
  • Put in place and enforce a coordinated vulnerability disclosure policy and a contact address for reporting vulnerabilities.
  • Distribute security updates securely and without delay, free of charge unless agreed otherwise for a tailor-made product.

Software bill of materials (SBOM)

Annex I Part II requires manufacturers to draw up an SBOM "in a commonly used and machine-readable format covering at the very least the top-level dependencies of the product". The Act does not name a format. SPDX and CycloneDX are widely used and meet the description, but the regulation does not require either one.

The SBOM forms part of the technical documentation. You do not have to publish it, but market surveillance authorities can ask for it. It lists components and versions. It is not a vulnerability report: vulnerability status comes from your monitoring process, which uses the SBOM as its inventory.

Many manufacturers will need software composition analysis tooling and a release process that regenerates the SBOM for each build. If you cannot yet say which open source libraries ship in each product version, building that inventory is a sensible first step.

Support period

Manufacturers must determine a support period for each product. Under Article 13(8) it reflects the time the product is expected to be in use and is at least five years, unless the product is expected to be in use for less than five years, in which case it matches that shorter period. The shorter period has to follow from how the product is expected to be used, not from the lifecycle the manufacturer would prefer commercially. The manufacturer takes into account user expectations, the nature of the product and relevant EU law when setting it.

During the support period, the manufacturer handles vulnerabilities in line with Annex I Part II. Each security update must remain available for at least ten years after it is issued, or for the rest of the support period if that is longer (Article 13(9)). The end date of the support period, at least month and year, must be shown clearly at the time of purchase and, where possible, on the product or its interface (Article 13(19)).

Reporting obligations since September 2026

Article 14 has applied since 11 September 2026. It applies to every product with digital elements on the EU market, including products placed on the market before December 2027. It contains two separate duties, each with its own deadlines.

StageActively exploited vulnerabilitySevere incident affecting the security of the product
Early warningWithout undue delay and within 24 hours of becoming awareWithout undue delay and within 24 hours of becoming aware
NotificationWithout undue delay and within 72 hours, with general information on the product, the exploit and corrective or mitigating measuresWithout undue delay and within 72 hours, with information on the nature of the incident, an initial assessment and measures taken
Final reportNo later than 14 days after a corrective or mitigating measure is availableWithin one month after the 72-hour incident notification

The clock starts when the manufacturer becomes aware of the facts that make something an actively exploited vulnerability or a severe incident. Do not wait for a CVE to be assigned or for the technical investigation to finish. If your support team receives evidence on Monday that customers are being attacked through a firmware flaw, the early warning is due on Tuesday, even if the CVE is published weeks later.

Both are submitted through the single reporting platform run by ENISA (Article 16). A notification goes to the CSIRT designated as coordinator in the member state of your main establishment and to ENISA at the same time. ENISA opened the platform on 11 September 2026. You file once and the coordinating CSIRT shares the notification with other member states where the product is sold. The manufacturer must also inform affected users about the vulnerability or incident and any mitigating measures they can take, where necessary in a structured, machine-readable format.

A severe incident under the CRA is not the same thing as a personal data breach. A CRA incident concerns the security of the product. It may or may not involve personal data. If it does, you assess the GDPR notification separately and report it to the data protection authority. One event can trigger both duties, with different recipients and deadlines.

24h
early warning for an actively exploited vulnerability or a severe incident
5 yrs
minimum support period unless the product is expected to be in use for less time
€15M
or 2.5% of worldwide turnover, maximum fine for breaching the essential requirements

Open source software

Free and open source software that is not made available in the course of a commercial activity is outside the CRA. Whether an activity is commercial needs a case-by-case analysis. Charging for the software, or monetising it through a related service or platform, points to a commercial activity. Contributing code to a project you do not control does not by itself make you a manufacturer, and a volunteer maintainer publishing software outside a commercial activity is not a manufacturer either.

The Act creates a separate role for open-source software stewards: legal persons, such as some foundations, that systematically provide sustained support for the development of free and open source software intended for commercial activities. Stewards must have a documented cybersecurity policy, cooperate with market surveillance authorities and report actively exploited vulnerabilities and severe incidents to the extent they are involved in development (Articles 3(14) and 24). Their obligations are lighter than a manufacturer's, and they are not subject to administrative fines (Article 64(10)).

If you are a manufacturer that ships open source components inside your own product, you remain responsible for those components. Annex I applies to the whole product, and you report vulnerabilities you find in a component to whoever maintains it.

The implementation timeline

10 Dec 2024
Entry into force
Regulation (EU) 2024/2847 enters into force. Most provisions apply later.
11 Jun 2026
Notification of conformity assessment bodies
Chapter IV applies. Member states can notify conformity assessment bodies so that third-party assessments are available before the main obligations start.
11 Sep 2026
Reporting obligations apply
Article 14 applies: reporting of actively exploited vulnerabilities and severe incidents through the single reporting platform.
11 Dec 2027
General application
The essential requirements, conformity assessment, CE marking, technical documentation, SBOM and support period obligations apply to products placed on the market from this date.

Products already on the market

Article 69 sets the transitional rules. A product placed on the EU market before 11 December 2027 is subject to the CRA only if it undergoes a substantial modification from that date. The reporting duties in Article 14 are the exception: they apply to all products with digital elements placed on the market, including those placed before 11 December 2027. This is not a blanket exemption: continuing to sell a version already on the market and placing new versions on the market have to be assessed against the transitional rules and the legal meaning of placing on the market. Do not assume that every product developed before December 2027 is exempt. EU-type examination certificates and approval decisions already issued for the cybersecurity requirements of other EU harmonisation legislation remain valid until 11 June 2028, unless they expire sooner.

What counts as a substantial modification is addressed in the Commission's July 2026 guidance. A security update that does not change the intended purpose is generally not one. A software update that adds functions or changes the risk profile may be.

CRA, NIS2 and GDPR compared

CRANIS2GDPR
What it regulatesProducts with digital elementsThe security of an entity's own network and information systems and servicesProcessing of personal data
Who it applies toManufacturers, importers, distributors and open-source software stewardsEssential and important entities in listed sectorsControllers and processors
What triggers reportingActively exploited vulnerability or severe incident affecting the productSignificant incident affecting the entity's servicesPersonal data breach likely to result in a risk to individuals
Who receives the reportCoordinating CSIRT and ENISA, through the single reporting platformNational CSIRT or competent authorityData protection authority, and individuals if the risk is high
Deadlines24 hours, 72 hours, then 14 days after a fix or one month24 hours, 72 hours, then one month72 hours to the supervisory authority where there is a risk; individuals without undue delay if the risk is high (Article 34)

A software company can sit under all three: the CRA for the products it sells, NIS2 for its own operations if it is in a covered sector, and GDPR wherever it processes personal data. For UK organisations, UK GDPR and the ICO apply to processing in the UK, and the NIS Regulations 2018 apply in place of NIS2.

Evidence to have ready

Market surveillance authorities will ask for documents, not intentions. This matrix lists what we would expect a manufacturer to be able to produce.

AreaRequirementEvidence
Scope and classificationArticles 2, 6 and 7, Annexes III and IVProduct inventory with role, core functionality, category and the reasoning behind it
Cybersecurity risk assessmentArticle 13(2) and (3)Documented risk assessment per product, updated during the support period
Security by designAnnex I Part ISecure development policy, default configuration records, test results
Vulnerability handlingAnnex I Part IICoordinated vulnerability disclosure policy, contact point, triage and remediation records
SBOMAnnex I Part II(1)Machine-readable SBOM per release, covering at least top-level dependencies
Support periodArticle 13(8), (9) and (19)Support period decision and rationale, end date shown at purchase, update availability records
Conformity assessmentArticle 32, Annex VIITechnical documentation, EU declaration of conformity, notified body certificate where needed, CE marking
Incident reportingArticle 14Registration on the single reporting platform, named reporters, escalation procedure, records of each report and user notification

What to do now

Reporting already applies, and the main obligations start on 11 December 2027. Technical documentation, SBOM tooling and third-party assessments all take time to set up, so plan the work now.

Step 1: Build the product inventory

List every product you develop, import or distribute in the EU, your role for each, and any remote data processing it depends on. Check each against the definition of a product with digital elements and the exclusions in Article 2.

Step 2: Classify by core functionality

Compare each product's core functionality with Annexes III and IV and the Commission's technical descriptions. If a product is Class II or critical, contact a notified body early, because capacity may be limited.

Step 3: Make reporting work

Register on the single reporting platform, name who can submit, and agree how a report of active exploitation reaches them within hours. Test the procedure against both the vulnerability and the incident timelines.

Step 4: Generate SBOMs and run vulnerability handling

Produce an SBOM for each release, connect it to vulnerability monitoring and publish a coordinated vulnerability disclosure policy with a contact address.

Step 5: Set support periods and plan documentation

Decide the support period for each product and show the end date at the point of sale. Start the technical documentation and risk assessment for products you will place on the market after 11 December 2027.

Our cybersecurity team supports manufacturers, importers and distributors with CRA readiness assessments, SBOM implementation and vulnerability handling design. Our compliance practice helps with technical documentation and conformity assessment preparation for UK businesses selling into the EU.


The fine structure

Market surveillance authorities in each member state enforce the CRA. Article 64 sets the maximum administrative fines:

  • Essential requirements and the obligations in Articles 13 and 14: up to €15 million or 2.5% of total worldwide annual turnover, whichever is higher.
  • Other obligations, including those of importers and distributors, conformity assessment and CE marking: up to €10 million or 2% of total worldwide annual turnover, whichever is higher.
  • Incorrect, incomplete or misleading information given to notified bodies or market surveillance authorities: up to €5 million or 1% of total worldwide annual turnover, whichever is higher.

Microenterprises and small enterprises cannot be fined for missing the 24-hour early warning deadline, and open-source software stewards cannot be fined (Article 64(10)). Authorities can also order corrective action, withdraw or recall products and restrict them across the EU.

Frequently asked questions

What is a product with digital elements under the Cyber Resilience Act?

It is any software or hardware product, including its remote data processing solutions, whose intended or reasonably foreseeable use includes a direct or indirect data connection to a device or network. Standalone SaaS is outside the CRA, but cloud processing that a product needs to perform one of its functions is covered as part of that product.

Does the Cyber Resilience Act apply to open source software?

Free and open source software made available outside a commercial activity is not in scope. Whether an activity is commercial needs case-by-case analysis; monetising the software or a related service points that way. Open-source software stewards have their own lighter obligations under Article 24 and are not subject to fines. A manufacturer that ships open source components in its product remains responsible for them.

When do the CRA reporting obligations apply?

Since 11 September 2026. Actively exploited vulnerabilities need an early warning within 24 hours, a notification within 72 hours and a final report no later than 14 days after a corrective measure is available. Severe incidents need an early warning within 24 hours, a notification within 72 hours and a final report within one month of the notification. Reports go through ENISA's single reporting platform to the coordinating CSIRT and ENISA.

Is an SBOM mandatory, and in which format?

Yes. Annex I Part II requires an SBOM in a commonly used, machine-readable format covering at least the top-level dependencies. The Act does not name a format; SPDX and CycloneDX are common choices. The SBOM is part of the technical documentation and does not have to be published, but authorities can request it.

What are the penalties under the Cyber Resilience Act?

Breaching the essential requirements or the obligations in Articles 13 and 14 can lead to fines of up to €15 million or 2.5% of worldwide annual turnover, whichever is higher. Other obligations carry up to €10 million or 2%, and misleading information up to €5 million or 1%. Microenterprises and small enterprises cannot be fined for missing the 24-hour early warning deadline.

Sources

Ryland Deakin
About the author
Lead Consultant, Cyvra · CISM · CompTIA Security+ · MCP

Ryland has delivered cybersecurity, compliance, and IT management programmes for regulated organisations across the UK and the Netherlands for over 20 years. View full profile

CRA Readiness

Need to assess your CRA exposure?

We help manufacturers, importers and distributors classify products, set up CRA reporting, build SBOM processes and prepare for December 2027.

Disclaimer: This article is for general informational purposes only and does not constitute legal, regulatory, or professional advice. Cyvra makes no warranty as to the accuracy or completeness of this content, which may not reflect the most current regulatory developments. Readers should seek independent legal and regulatory advice appropriate to their specific circumstances. Cyvra accepts no liability for any loss arising from reliance on this content.