Is your product in scope of the CRA? Five questions that decide it
Scope under the Cyber Resilience Act turns on five questions. Most products answer them quickly; the ones that do not need a written rationale.
Most teams ask “are we in scope?” as one question. The regulation answers it as five, and the order matters. You can work through the same questions in our CRA checker.
1. Is it a product with digital elements?
Software, or hardware with software or firmware in it, including its remote data processing solutions (Art. 3(1)). A purely mechanical product is out. Almost anything with a microcontroller is in.
2. Does it connect, directly or indirectly?
The CRA applies where the product’s intended purpose or reasonably foreseeable use includes a direct or indirect data connection to a device or network (Art. 2(1)). “Indirect” does a lot of work here. A device that is only ever updated over USB, or that talks to a phone app that talks to the internet, is connected.
3. Is it made available on the EU market in a commercial activity?
Selling into the EU counts, online sales included. Free products count too when they are monetised. Open-source software published outside a commercial activity is outside the regulation for its developers. An organisation that systematically supports open-source software for commercial use may be an open-source steward, with lighter duties (Art. 24).
4. Does a sector regulation take it out?
Medical and in vitro diagnostic devices, type-approved vehicles, certified civil aviation products and marine equipment have their own cybersecurity rules and are excluded (Art. 2). So are products developed exclusively for national security or defence.
The exclusion covers the regulated product only. An app, gateway or accessory sold separately from an excluded device can still be in scope on its own.
5. What is the core function?
If you are in scope, class decides the conformity route. A product is important (Annex III) or critical (Annex IV) only if its core functionality is one of the listed categories (Art. 7(1)). A smart thermostat that runs an embedded operating system is not an operating system. A router is a router.
| Class | Typical route |
|---|---|
| Default | Self-assessment, Module A |
| Important, Class I | Module A with harmonised standards applied in full; otherwise a notified body |
| Important, Class II | A notified body, Modules B and C or Module H |
| Critical | A European cybersecurity certificate where required |
Where answers need writing down
The quick cases are quick. The ones that take an argument are products with several functions near an Annex III category, products whose cloud service may or may not be remote data processing, and products that pass through several hands. For those, the reasoning matters as much as the answer: it’s the first thing a market surveillance authority asks for.
Writing that reasoning down is the first part of our CRA assessment: scope and class in writing, with the argument for any borderline call.
Talk to us
Book a 30-minute call
Tell us what the product does and where you sell it. We'll talk through what the CRA is likely to ask of it, and whether an assessment is worth doing.
Book a call or email [email protected]
Useful to have to hand
- What the product is and how it connects
- Where you sell it, and who places it on the EU market
- How often you release software or firmware
- Any date you're working towards