---
title: "CRA Applicability Check: Is Your Product in Scope? Free Tool"
description: "CRA applicability check: find out free of charge whether your product falls under the Cyber Resilience Act, which class applies and what comes next."
url: https://panther.blue/en/cra/applicability-check/
lang: en
date_modified: 2026-10-26
author: David Kleinz (Blue Panther GmbH)
alternate: https://panther.blue/cra/betroffenheitscheck/
---

# CRA Applicability Check: Does Your Product Fall Under the Cyber Resilience Act?

_As of: 26 October 2026 · Author: David Kleinz, CISSP, ISO/IEC 27001 Lead Auditor · https://panther.blue/en/cra/applicability-check/_

**In short:** A product falls under the CRA if it is hardware or software with a direct or indirect data connection, is placed on the EU market and no Art. 2 exclusion applies (e.g. medical devices, vehicles, non-commercial open source). The free check answers this in eight questions and names the product class, conformity route and deadlines; all inputs stay in your browser.

The CRA applicability check uses a few questions to determine whether your product is a product with digital elements within the meaning of Regulation (EU) 2024/2847, whether an exclusion applies and which product class it falls into. The result shows you the appropriate conformity route and the deadlines that apply to you.

## How the check works

The check asks you, one after another, the questions an assessor would ask: Does your product have a data connection? Does an exclusion under Art. 2 CRA apply? Do you make it available under your own name? And what is its core function? From the answers, it derives whether the [Cyber Resilience Act](https://panther.blue/en/cra/) applies, which product class fits and which conformity assessment procedure follows. The check runs entirely in your browser. No data is transmitted or stored; you can copy the result as text at the end.

## When a product falls under the CRA

The scope is defined in Art. 2 and Art. 3 of Regulation (EU) 2024/2847. Covered are products with digital elements that are made available on the Union market and whose intended purpose or reasonably foreseeable use includes a direct or indirect logical or physical data connection to a device or network. Three characteristics are decisive:

- **Software or hardware product.** This includes devices, firmware, operating systems, applications, apps, libraries and remote data processing solutions that are necessary for the product to function (Art. 3(1) and (2)).

- **Data connection.** Ethernet, fieldbus, Wi-Fi, Bluetooth, USB, cellular or any interface over which data is exchanged. "Indirect" means that a sensor that communicates only via a gateway is also covered.

- **Commercial supply.** The product is made available on the Union market in the course of a commercial activity, whether in return for payment or free of charge if a commercial purpose is pursued.

Typical examples from our target group: controllers, drives, industrial PCs, sensors with IO-Link, HMI panels, gateways, remote maintenance solutions, configuration software, spare parts with firmware, apps for operating devices, cloud backends for connected devices. Anyone who makes such products available under their own name is a manufacturer under Art. 13, even if they buy in the hardware (Art. 21). Importers (Art. 19) and distributors (Art. 20) have their own, lesser obligations.

## Exclusions

Art. 2(2) to (8) excludes products that are already subject to cybersecurity requirements under other EU legal acts or that lie outside internal market law:

| Exclusion | Legal basis | Note |
|---|---|---|
| Medical devices and in vitro diagnostics | Regulations (EU) 2017/745 and 2017/746 | Fully excluded; cybersecurity follows from the MDR and MDCG guidance. |
| Motor vehicles and vehicle systems with type approval | Regulation (EU) 2019/2144 | Excluded to the extent that type approval applies (UN R155/R156). Retrofit products and workshop software outside type approval remain covered. |
| Civil aviation | Regulation (EU) 2018/1139 | Excluded for products subject to EASA certification. |
| Marine equipment | Directive 2014/90/EU | Excluded. |
| Products exclusively for national security and defence | Art. 2(7) | Including products developed specifically for processing classified information. |
| Non-commercial open-source software | Art. 2 and recitals | Free software outside a commercial activity is not covered. Anyone who integrates it into a commercial product bears responsibility for the product (Art. 13(5)). Open-source software stewards are subject to a light regime (Art. 24). |

Not excluded: products for in-house use that are later sold after all; industrial products for closed networks; products "without internet" that nevertheless have a local interface. The data connection does not have to lead to the internet for the CRA to apply. For devices in OT environments, this is the most common misjudgement.

## What the result means

The check assigns your product to one of the four classes under Art. 32. The conformity route follows from that:

| Result | Conformity route | What you should do now |
|---|---|---|
| Not in scope | No CRA obligations | Document the reasoning, reassess when the product changes. Check whether your company falls under [NIS-2](https://panther.blue/en/nis-2/applicability-check/) as an operator. |
| Default product | Self-assessment, module A | Risk assessment, Annex I requirements, technical documentation, EU declaration of conformity, CE marking by 11 December 2027. |
| Important product, class I | Module A only with full application of harmonised standards, otherwise module B+C or H with a notified body | Since no standard has been cited as of October 2026: approach an assessment body and build documentation that is ready for assessment. |
| Important product, class II | Module B+C or H with a notified body | Engage an assessment body early; include assessment duration and waiting time in release planning. |
| Critical product | As class II, later European certification under the CSA | Monitor delegated acts; prepare for the certification scheme. |

Regardless of the class, the [reporting obligation under Art. 14](https://panther.blue/en/cra/reporting-obligations/) has applied since 11 September 2026 to all products on the market. The complete dates are in the [CRA timeline](https://panther.blue/en/cra/timeline/), and the details on classes and modules on the page on [CRA product classes](https://panther.blue/en/cra/product-classes/).

> **The check is an initial assessment, not legal advice.** It works with your answers and the categories in Annexes III and IV. Borderline cases, such as devices with several core functions, products at the interface with the Machinery Regulation or the Radio Equipment Directive, or software with optional connectivity, require a case-by-case review against the Commission's guidelines. Responsibility for the classification remains with the manufacturer.

## Next steps

If the check shows a product in scope, read next which [requirements from Annex I](https://panther.blue/en/cra/requirements/) are coming your way and how much time remains until 11 December 2027. In our [CRA consulting](https://panther.blue/en/cra/consulting/), we review your classification for the entire portfolio, clarify borderline cases with reasoning for the technical documentation and prepare the gap analysis as the basis for your implementation plan.

## Frequently asked questions

**Does pure software fall under the CRA?**

Yes. Products with digital elements include software and hardware products, provided their intended purpose includes a direct or indirect data connection (Art. 3(1)). Desktop applications, apps, firmware and libraries that are made available commercially are also covered. Only non-commercial open-source software is excluded.

**My product is a machine with a controller. CRA or Machinery Regulation?**

Both. The Machinery Regulation governs functional safety, the CRA the cybersecurity of the digital elements. The controller, the firmware and an associated app are products with digital elements. For the evidence, you can coordinate both conformity assessments, but they cannot replace each other.

**What about software as a service?**

Pure cloud services without a product link do not fall under the CRA but possibly under NIS-2. Remote data processing solutions without which a product cannot perform its function, such as the backend of an app or the cloud connection of a device, are part of the product and are covered (Art. 3(1) in conjunction with Art. 3(2)).

**I buy in devices and sell them under my own name. Am I a manufacturer?**

Yes. Anyone who places a product with digital elements on the market under their own name or trademark is deemed a manufacturer under Art. 21 with all obligations under Art. 13 and 14. The same applies to anyone who substantially modifies a product (Art. 22).

**Is the result of the check legally binding?**

No. The check provides an initial assessment based on your answers. The binding classification is made by you as the manufacturer in the technical documentation; in borderline cases, you should consult the Commission's guidelines on the scope and, if necessary, seek professional advice.

## Sources

- [Regulation (EU) 2024/2847 (CRA), Art. 2, 3, 21, 22, 32 and Annexes III, IV, EUR-Lex](https://eur-lex.europa.eu/eli/reg/2024/2847/oj)
- [European Commission: Cyber Resilience Act, guidelines on the scope (27 July 2026)](https://digital-strategy.ec.europa.eu/en/policies/cyber-resilience-act)
- [European Commission: CRA Summary](https://digital-strategy.ec.europa.eu/en/policies/cra-summary)
- [BSI, the German Federal Office for Information Security: Cyber Resilience Act](https://www.bsi.bund.de/DE/Themen/Unternehmen-und-Organisationen/Informationen-und-Empfehlungen/Cyber_Resilience_Act/cyber_resilience_act_node.html)

Cite as: Blue Panther GmbH (David Kleinz): “CRA Applicability Check: Does Your Product Fall Under the Cyber Resilience Act?”, panther.blue, as of 26 October 2026, https://panther.blue/en/cra/applicability-check/
