Does the Cyber Resilience Act apply to my product?
Last verified: 2026-11-20.
Information, not legal advice. Our reading of the official sources, not reviewed by a lawyer. You decide how the CRA applies to your product; for an opinion you can rely on, ask a lawyer; for a third-party conformity assessment, a notified body. This guide helps you work with the EU Cyber Resilience Act (Regulation (EU) 2024/2847) but does not certify, assess or guarantee the compliance of any product. You remain responsible for your product's conformity assessment, CE marking and reporting. Last verified against official sources: 2026-11-20.
Short answer
- In principle, yes, if you make available on the EU market a software or hardware product, or a component sold separately, whose intended purpose or reasonably foreseeable use includes a direct or indirect logical or physical data connection to a device or network (CRA Art. 2(1), 3(1)).
- "Made available" means supplied for distribution or use on the EU market in the course of a commercial activity, whether for payment or free of charge (CRA Art. 3(22)).
- Excluded: products covered by the EU rules on medical devices, in vitro diagnostic medical devices or vehicle type-approval; products holding a certification under the EU civil aviation rules; marine equipment; identical spare parts; and products developed or modified exclusively for national security or defence (CRA Art. 2(2)–(4), (6)–(7)).
- SaaS and browser-only web apps are not products with digital elements on their own. Processing at a distance is covered only as part of a product that needs it to perform one of its functions (CRA Art. 3(2), Recital 12; Commission guidance, points 20–21).
- Free and open-source software (FOSS) is covered only when it is made available in the course of a commercial activity, for example when it is monetised. Legal persons that sustain FOSS intended for commercial activities can be "open-source software stewards" with lighter duties (CRA Recitals 15, 18–19, Art. 3(14), 24).
What counts as a product with digital elements
A product with digital elements is "a software or hardware product and its remote data processing solutions, including software or hardware components being placed on the market separately" (CRA Art. 3(1)): for example apps, connected devices, laptops or integrated circuits (Guidance, point 18). It must be supplied in the course of a commercial activity. Signs of that include charging a price, charging for support beyond cost recovery, monetising other services through the product, requiring personal data for purposes other than security, compatibility or interoperability, and accepting donations above the product's costs (CRA Recital 15).
What is excluded
| The CRA does not apply to | Article |
|---|
| Products to which Regulation (EU) 2017/745 (medical devices), 2017/746 (in vitro diagnostic medical devices) or 2019/2144 (vehicle type-approval) applies | Art. 2(2); Recitals 25, 27 |
| Products that hold a certification under Regulation (EU) 2018/1139 (civil aviation) | Art. 2(3); Recital 27 |
| Equipment within the scope of Directive 2014/90/EU (marine equipment) | Art. 2(4) |
| Spare parts that replace identical components and are made to the same specifications | Art. 2(6); Recital 29 |
| Products developed or modified exclusively for national security or defence, or specifically designed to process classified information | Art. 2(7); Recital 26 |
The CRA also never requires you to supply information whose disclosure would be contrary to Member States' essential national security, public security or defence interests (CRA Art. 2(8)). The Commission may limit or exclude the CRA for further products by delegated act where sector rules give the same or a higher level of protection (CRA Art. 2(5)).
SaaS, web apps and remote data processing
Remote data processing is processing at a distance, designed and developed by the manufacturer or under its responsibility, without which the product could not perform one of its functions (CRA Art. 3(2)). Cloud functions that let users control a smart home device at a distance are in scope; websites that do not support a product's functionality, and cloud services designed outside the manufacturer's responsibility, are not. Recital 12 also recalls that NIS2 (Directive (EU) 2022/2555) applies to cloud computing services such as SaaS, PaaS and IaaS (CRA Recital 12).
In the Commission's reading, a mobile app or a locally installed desktop app is a product; a web app used only through a browser is not, unless it supports the functionality of a product; and a website that only presents information is out of scope (Guidance, points 20–21, Examples 3–6). Internal systems such as HR, CRM or CI/CD pipelines are not remote data processing (Guidance, point 182).
Free and open-source software
Free and open-source software (FOSS) is software whose source code is openly shared and which is licensed so that it is freely accessible, usable, modifiable and redistributable (CRA Art. 3(48)). FOSS that its manufacturer does not monetise is not supplied in the course of a commercial activity; financial support or regular releases do not change that on their own; and people who contribute code to FOSS not under their responsibility are not covered (CRA Recital 18). In the Commission's reading, charging a price for the software makes you its manufacturer, and with a paid and a free "community" version, only the paid one is placed on the market (Guidance, points 51–52).
An open-source software steward is a legal person, other than a manufacturer, that systematically supports on a sustained basis the development of specific FOSS intended for commercial activities and ensures its viability (CRA Art. 3(14)). From 11 December 2027, stewards must document a cybersecurity policy, cooperate with market surveillance authorities and report to the extent set out in Article 24(3) (CRA Art. 24, 71(2)). They may not affix the CE marking and face no administrative fines under the CRA (CRA Recital 19, Art. 64(10)(b)).
About the Commission guidance
The Commission published its guidance on applying the CRA as Communication C/2026/6013 in the Official Journal (C series) on 17 November 2026 (Guidance; Commission library page). It is not binding; only the Court of Justice of the EU can give an authoritative interpretation, and its examples do not replace a case-by-case assessment (Guidance, point 8).
To check this for your product with an AI assistant, add Shieldbook to Claude or connect the Shieldbook MCP server (https://shieldbook.ppftec.com/mcp); the scope check is also at https://shieldbook.ppftec.com/check.
FAQ
Is my SaaS product covered by the CRA?
Not if it is only a service used through a browser that does not support the functions of a product you supply. If you also supply an app, device or client that needs your back end to perform one of its functions, that back end is part of the product as remote data processing (CRA Art. 3(1)–(2), Recital 12; Guidance, points 21, 178).
I publish an open-source library for free. Am I a manufacturer?
Not for that library if you do not monetise it (CRA Recital 18). If you are a legal person that supports it on a sustained basis and it is intended for commercial activities, you may be its steward (CRA Art. 3(14), 24; Guidance, points 67–68).
Does the CRA cover products I placed on the market before December 2027?
The CRA's requirements apply to them only if they undergo a substantial modification from 11 December 2027, but the Article 14 reporting duties have applied to them since 11 September 2026 (CRA Art. 69(2)–(3), 71(2)).
Sources
Opened by the compliance analyst; dates are when each source was last read.
- Regulation (EU) 2024/2847 (Cyber Resilience Act), OJ L, 20.11.2024. Citation URL: https://eur-lex.europa.eu/eli/reg/2024/2847/oj/eng. File read (authentic OJ PDF via the Publications Office): https://publications.europa.eu/resource/cellar/21b7d4eb-a6e2-11ef-85f0-01aa75ed71a1.0006.01/DOC_1. Recitals 12, 14–19, 25–27, 29, Art. 2, 3(1)–(22), 3(48), 24, 64(10), 69 and 71 read 2026-11-20.
- European Commission, Commission guidance on the application of Regulation (EU) 2024/2847 (Cyber Resilience Act), Communication C/2026/6013, OJ C, 17.11.2026, not binding (point 8). Citation URL: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=OJ:C_202606013. File read (OJ C PDF via the Publications Office): https://publications.europa.eu/resource/cellar/dcbc848b-e227-11f1-aefc-01aa75ed71a1.0006.01/DOC_1. Points 8, 13–21, 40–54, 65–78 and 178–191 read 2026-11-20.
- European Commission, library page "Commission publishes new guidance to support timely Cyber Resilience Act implementation", last update 18 November 2026: https://digital-strategy.ec.europa.eu/en/library/commission-publishes-new-guidance-support-timely-cyber-resilience-act-implementation (2026-11-20).
The Shieldbook kit: templates and worked examples
This site needs JavaScript for the scope checker and the waitlist form.