Customize this training

Get a certificate — $16.67$5

EU Cyber Resilience Act (CRA) for Product Manufacturers

EU Cyber Resilience Act (CRA) for Product Manufacturers

Check whether your hardware or software is in CRA scope, pick the right conformity route, build in the essential requirements, handle vulnerabilities and report exploited flaws to the CSIRT within 24 hours.

What you will learn

  • Explain what the CRA is, why it was adopted and its three key application dates.
  • Decide whether a product is in scope and which economic operator role your company holds.
  • Classify a product as default, important (class I or II) or critical and choose its conformity assessment route.
  • Apply the Annex I Part I essential cybersecurity requirements during design and development.
  • Run vulnerability handling over the support period: SBOM, disclosure policy, free security updates.
  • Report actively exploited vulnerabilities and severe incidents on time through the single reporting platform.
  • Prepare the technical documentation, declaration of conformity and CE marking, and plan readiness before December 2027.

Modules

  1. The CRA at a glance: why and when
  2. Scope and roles: who must do what
  3. Product categories and conformity assessment
  4. Secure by design: the Annex I Part I requirements
  5. Vulnerability handling over the support period
  6. Reporting exploited vulnerabilities and severe incidents
  7. Documentation, CE marking, penalties and your roadmap

Course facts

Level
Awareness
Estimated study time
about 45 minutes
Final assessment
28 questions · Pass mark 80%
Available in
English, Français
Price
Free. Optional verifiable certificate: $5
Last updated
Published by
AMAADOR ACADEMY

Who this course is for

Product managers, engineers, security and compliance staff, quality and regulatory teams at manufacturers, software publishers, importers and distributors that sell connected products or software in the EU, including suppliers in Morocco, the GCC and elsewhere.

Prerequisites

None. A general idea of how your products are designed, updated and sold helps.

Course content

1. The CRA at a glance: why and when

Before the Cyber Resilience Act, most EU product laws said nothing precise about cybersecurity. A router, a smart lock or a desktop application could be sold with default passwords, no update mechanism and no one to contact about a flaw. Buyers had no way to tell a secure product from an insecure one, and many manufacturers stopped patching soon after launch.

Regulation (EU) 2024/2847, the Cyber Resilience Act (CRA), changes this. It is a regulation, so it applies directly in every Member State without a national transposition law. It sets horizontal rules for products with digital elements: hardware and software whose intended or foreseeable use includes a data connection to a device or network.

The five ideas that run through the whole Regulation.

The CRA works like other EU product safety laws (the "New Legislative Framework"). The manufacturer assesses its product against essential requirements, writes technical documentation, signs an EU declaration of conformity and affixes the CE marking. National market surveillance authorities then check products on the market and can order corrections, withdrawals or recalls.

2. Scope and roles: who must do what

Article 3(1) defines a product with digital elements as a software or hardware product and its remote data processing solutions, including software or hardware components placed on the market separately. The CRA covers it when its intended or reasonably foreseeable use includes a direct or indirect data connection to a device or network.

In practice the scope is very wide: smartphone apps, operating systems, games, firmware, routers, cameras, smart TVs, industrial controllers, connected toys, and also components such as a microcontroller or a software library sold on its own.

Remote data processing is covered only when it is designed by the manufacturer (or under its responsibility) and the product could not perform one of its functions without it. The cloud back end of a smart camera app is in; a general-purpose SaaS sold on its own is not a product with digital elements (other EU rules such as NIS2 may apply to it).

Out of scope (Article 2)Why
Medical and in vitro diagnostic devices (Regulations 2017/745 and 2017/746)Covered by their own sector rules
Motor vehicles under type-approval Regulation 2019/2144Sector cybersecurity rules exist
Civil aviation products certified under Regulation 2018/1139Sector certification
Marine equipment under Directive 2014/90/EUSector rules
Identical spare parts made to the same specificationsReplace an already compliant component
Products developed or modified exclusively for national security or defenceOutside EU product law

3. Product categories and conformity assessment

The CRA sorts products by how much harm an attack on them could cause. The category does not change the essential requirements, which apply to all. It changes how conformity must be demonstrated.

CategoryWhere listedExamples
DefaultEverything not listedMost products: household appliances, games, mobile apps, printers, many industrial devices
Important, class IAnnex III, 19 categoriesOperating systems, browsers, password managers, anti-malware, VPN products, SIEM, routers and modems, boot managers, smart home security products (locks, cameras, baby monitors, alarms), connected toys with social or location features, health wearables not covered by medical device rules
Important, class IIAnnex III, 4 categoriesHypervisors and container runtimes, firewalls, intrusion detection and prevention systems, tamper-resistant microprocessors and microcontrollers
CriticalAnnex IVHardware devices with security boxes, smart meter gateways and devices for advanced security purposes, smartcards and secure elements

The test is the product's core functionality. A product is important because its main function matches an Annex III category, not because it contains such a component. A smart fridge that embeds a small operating system is not an "operating system" product. The operating system sold to the fridge maker is.

4. Secure by design: the Annex I Part I requirements

Article 13 requires the manufacturer to carry out a cybersecurity risk assessment of the product and to take it into account in planning, design, development, production, delivery and maintenance. The assessment must be documented, updated during the support period and included in the technical documentation.

Annex I Part I then sets the product properties. Point 1 is the general rule: the product must be designed, developed and produced to ensure an appropriate level of cybersecurity based on the risks. Point 2 lists what the risk assessment must address. Not every item fits every product, but you must explain in the file why an item does not apply.

  1. Describe the product — intended purpose, reasonably foreseeable use and misuse, operating environment, users
  2. Map assets and interfaces — data, functions, radio, ports, APIs, cloud back end, update channel
  3. Identify threats — who would attack, how, and what they would gain
  4. Rate the risks — likelihood and impact for users and for other networks
  5. Choose controls — map each Annex I item to a design decision or a justified exclusion
  6. Keep it alive — update after new vulnerabilities, incidents or design changes

5. Vulnerability handling over the support period

Annex I Part II applies to the manufacturer's processes, not to the product itself. It must be met for as long as the support period lasts.

  1. Identify and document vulnerabilities and components, including a machine-readable software bill of materials (SBOM) covering at least top-level dependencies
  2. Remediate without delay, with security updates provided separately from feature updates where technically feasible
  3. Test and review the product's security regularly and effectively
  4. Disclose fixed vulnerabilities publicly once an update is available, with a description, affected products, impact, severity and remediation advice (publication may be delayed in justified cases until users can patch)
  5. Have a coordinated vulnerability disclosure (CVD) policy and enforce it
  6. Make reporting easy: a contact address for reporting vulnerabilities and sharing information
  7. Distribute updates securely, automatically where applicable
  8. Disseminate updates without delay and free of charge, with advisory messages telling users what to do

The SBOM goes in the technical documentation. It does not have to be published, but a market surveillance authority can request it. Formats such as SPDX or CycloneDX are widely used to make it machine-readable.

6. Reporting exploited vulnerabilities and severe incidents

Since 11 September 2026, Article 14 requires manufacturers to report two kinds of events affecting any of their products with digital elements on the EU market, old or new.

EventDefinitionExample
Actively exploited vulnerabilityA vulnerability for which there is reliable evidence that a malicious actor has exploited it in a system without the owner's permission (Art. 3(42))Your support team sees routers being taken over through a flaw in your web interface
Severe incident having an impact on the security of the productAn incident that affects, or can affect, the product's ability to protect the availability, authenticity, integrity or confidentiality of sensitive or important data or functions, or that has led or can lead to malicious code being introduced or run in the product or users' systems (Art. 14(5))An attacker breaks into your build server and plants code in the next update

What does not trigger the mandatory report: a vulnerability found by your own testing, a researcher's responsible disclosure or a bug bounty, as long as there is no evidence of malicious exploitation (recital 68). It still has to be fixed under Annex I Part II, and you can report it voluntarily.

7. Documentation, CE marking, penalties and your roadmap

Before a product is placed on the market from 11 December 2027, the manufacturer must hold evidence that it complies. Annex VII lists the technical documentation:

Annex VII itemContent
1General description: intended purpose, software versions, photos for hardware, user information (Annex II)
2Design, development, production and vulnerability handling: architecture, SBOM, CVD policy, contact address, secure update method
3Cybersecurity risk assessment and how each Part I requirement is applied
4Information used to set the support period
5Harmonised standards, common specifications or certification schemes applied, in full or in part, and other solutions used
6Test reports showing conformity with Parts I and II
7Copy of the EU declaration of conformity
8The SBOM, where applicable, on reasoned request of a market surveillance authority

The EU declaration of conformity (Article 28, model in Annex V) states that the essential requirements are met. By signing it the manufacturer takes responsibility for compliance. Where several EU acts apply, for example the Radio Equipment Directive, one single declaration covers them all. The user receives a copy or a simplified declaration giving the internet address of the full one.

The full lesson continues in the interactive course on this page.

Sources and references

Education only, not legal advice. Based on Regulation (EU) 2024/2847 as published in the Official Journal of the EU and on European Commission CRA pages, as of November 2026. Harmonised standards, implementing and delegated acts and national enforcement rules are still being completed. Check the current texts and a qualified adviser before deciding your product's category or conformity route.

All courses · Data Privacy & Governance — Free certified training | AMAADOR ACADEMY