The Cyber Resilience Act (CRA) sets mandatory security requirements for hardware and software sold in the EU. Since 11 September 2026, manufacturers must report exploited vulnerabilities and incidents; the other obligations apply from 11 December 2027. A short overview of who it affects and what to do.
What is the CRA and when does it apply?
The Cyber Resilience Act (CRA) is an EU regulation requiring hardware and software sold in the EU to be designed securely, updated for a defined period and CE marked. While NIS2 regulates organisations, the CRA regulates the product itself.
- since 11 Sep 2026 – obligation to report actively exploited vulnerabilities and severe incidents, also for products sold earlier,
- from 11 Dec 2027 – all other obligations: security requirements, conformity assessment, documentation and CE marking.
Which products does the CRA cover?
Any hardware and software that connects to a device or network and is sold in the EU – e.g. routers, smart locks, cameras and watches, baby monitors, industrial sensors, operating systems, mobile apps or firmware.
- Cloud is covered only as the manufacturer's backend without which the product does not work – e.g. an API its mobile app needs. An informational website or a stand-alone SaaS service is not covered.
- Exclusions: medical devices, vehicles, aviation, marine equipment, defence and spare parts.
Open source: when is it a commercial activity?
The CRA applies only to products supplied in the course of a commercial activity. For open-source software, what matters is therefore not how it was developed or financed, but whether the manufacturer monetises it.
| Commercial activity (CRA applies) | Not a commercial activity (CRA does not apply) |
|---|---|
| A price is charged for the software. | The manufacturer does not monetise the project. |
| A price is charged for technical support that does not merely recover actual costs. | The project receives financial support from companies, or companies contribute to its development – this alone is not enough. |
| The manufacturer provides a software platform through which it monetises other services. | The project has regular releases – this alone does not mean commercial activity either. |
| Use is conditional on processing personal data for purposes other than exclusively improving security, compatibility or interoperability. | Development by a not-for-profit organisation that uses all earnings after costs for not-for-profit objectives. |
| Donations exceeding the costs of designing, developing and providing the product are accepted. | Donations without the intention of making a profit; contributors of code to projects that are not under their responsibility. |
An open-source component intended for integration into other manufacturers' products is considered made available on the market only if it is monetised by its original manufacturer.
Practical example: a Czech company develops an IoT gateway and uses a library from GitHub that nobody monetises. The library itself is outside the CRA, but the gateway manufacturer is responsible for the entire product including that component – it must exercise due diligence and report any vulnerability it finds to the library's maintainer and remediate it.
What are the product categories?
| Category | Examples | Conformity assessment |
|---|---|---|
| Default (most products) | Ordinary apps, games, printers, smart appliances | Manufacturer itself |
| Important (class I and II) | Password managers, VPNs, antivirus, operating systems, routers, smart locks and cameras, toys, firewalls | Often a third party |
| Critical | Smartcards, secure elements, smart meter gateways | European certification |
Core functionality decides: a smart TV with a built-in browser is not a “browser”.
What are the manufacturer's obligations?
- design the product securely – no known vulnerabilities, secure default settings,
- check third-party components, including open source, and keep a list of them (SBOM),
- provide security updates for at least 5 years (longer for routers or operating systems) and state the end of support at the time of purchase,
- have a contact point for reporting vulnerabilities – a chatbot is not enough,
- assess conformity, draw up documentation and affix the CE marking.
Note: anyone selling a product under their own brand is the manufacturer – e.g. an e-shop selling smart cameras made in Asia under its private label.
What must be reported and when?
Since 11 September 2026, manufacturers report via ENISA's platform (in the Czech Republic to the governmental CERT at NÚKIB) any actively exploited vulnerability and severe incident, for example when an attacker sneaks malicious code into updates.
- within 24 hours an early warning,
- within 72 hours a notification,
- within 14 days after a fix (one month for incidents) a final report.
Example: a smart camera manufacturer discovers on Friday at 8 pm that attackers are bypassing login. It must file the warning by Saturday 8 pm and inform users at the same time.
What fines can be imposed?
Up to EUR 15 million or 2.5% of worldwide turnover for breaching security requirements and reporting, up to EUR 10 million or 2% for other obligations. Micro and small enterprises cannot be fined for missing the 24-hour deadline. In the Czech Republic, supervision will be carried out mainly by the Czech Trade Inspection Authority.
What to do now?
- List the products you sell in the EU, including older ones.
- Determine your role and your products' category.
- Decide who files the 24-hour report and how – including at weekends.
- Update your contracts with component suppliers.
- Set the support period and state it in your terms and conditions.
Summary
The CRA covers virtually any hardware and software that connects to a device or network and is supplied to the EU market in the course of a commercial activity. The reporting obligation has applied since 11 September 2026, also to products sold earlier; the essential requirements, conformity assessment and CE marking apply from 11 December 2027. The key steps are determining your role and product category and setting up a 24-hour reporting process, support periods and component checks.
How we can help:
- we assess whether and how the CRA applies to your products and services and determine your role and product categories,
- we set up an internal process for reporting vulnerabilities and incidents and a coordinated vulnerability disclosure policy,
- we amend contracts with component suppliers and customers, your terms and conditions and support-period information (business law),
- we help with the legal assessment of open-source models and licences,
- we align CRA requirements with NIS2 and the AI Act (AI compliance).
If you are not sure what the CRA means for you, get in touch – we will be glad to help.
You may also be interested in:
Frequently asked questions
Answers to the questions our clients ask us most often.
Which products does the Cyber Resilience Act (CRA) apply to?
Hardware and software that connects to a device or network and is sold in the EU – e.g. routers, smart locks, mobile apps or firmware. Exclusions include medical devices, vehicles and defence.
When do manufacturers have to report vulnerabilities and incidents under the CRA?
Since 11 September 2026, also for products sold earlier. Early warning within 24 hours, notification within 72 hours and a final report within 14 days after a fix (one month for incidents).
Is a mobile app, cloud service or SaaS covered by the CRA?
A mobile app is. Cloud only as the manufacturer's backend without which the product does not work. A stand-alone SaaS service falls under NIS2, not the CRA.
Does the CRA apply to open-source software?
Only if the manufacturer monetises it. A company that builds an open-source component into its product is, however, responsible for it.
How long must a manufacturer provide security updates under the CRA?
At least 5 years, longer for long-lived products (routers, operating systems). The end of support must be stated at the time of purchase.
What fines can be imposed for infringing the CRA?
Up to EUR 15 million or 2.5% of worldwide turnover. Micro and small enterprises cannot be fined for missing the 24-hour deadline.
Does the CRA apply to products already on the market before 11 December 2027?
Reporting does, since 11 September 2026. The other requirements only if the product undergoes a substantial modification after 11 December 2027, e.g. an update adding a new feature.