Article 2

Scope and Exclusions Under the Cyber Resilience Act

Article 2 defines the scope of the CRA - which products and economic operators are covered - and sets out important exclusions for sectors already regulated under other EU frameworks. Understanding the scope boundaries is critical for manufacturers who operate across multiple product categories or who supply products to regulated industries such as medical devices, aviation, or automotive. Where exclusions apply, the CRA does not impose additional obligations, but the underlying sector regulation typically has its own cybersecurity requirements.

Effective: December 2027Applies to: Manufacturers of products with digital elements placed on the EU marketLast reviewed: 28 October 2026Verified against: the final text of Regulation (EU) 2024/2847
Source: Regulation (EU) 2024/2847, Article 2, official text on EUR-Lex

General Scope: Products with Digital Elements

Article 2(1) applies the CRA to products with digital elements that are placed on the market or put into service in the EU, where those products have a direct or indirect logical or physical data connection to a device or network. This captures a very broad range of hardware and software products - from consumer IoT devices and industrial sensors to operating systems, firmware, and standalone software applications.

The key qualifying condition is the network or device connection. A purely mechanical product with no digital components falls outside the scope. However, a product that includes an embedded microcontroller with network capability, even if that capability is not its primary function, is likely within scope. Manufacturers of complex multi-component systems should assess each component independently as well as the system as a whole.

CRA reference:Article 2(1)

Excluded Sectors: Medical Devices and IVDs

Products regulated under the EU Medical Device Regulation (MDR, Regulation 2017/745) and the In Vitro Diagnostic Medical Devices Regulation (IVDR, Regulation 2017/746) are excluded from CRA scope. These regulations already impose cybersecurity requirements on medical devices, including post-market surveillance and incident reporting obligations.

Manufacturers of medical devices that connect to networks must still comply with MDR/IVDR cybersecurity requirements, which are enforced through notified bodies and the EUDAMED database. The practical effect of the exclusion is that medical device manufacturers do not face dual obligations under both the CRA and MDR/IVDR - the sector-specific regime prevails.

Note that this exclusion applies to the device itself. Software that is a medical device (SaMD) is excluded, but general-purpose software that interfaces with a medical device but is not itself a medical device is not automatically excluded.

CRA reference:Article 2(2)(a), Article 2(2)(b)

Excluded Sectors: Aviation, Vehicles, and Maritime

Article 2(3) excludes products with digital elements that are certified in accordance with Regulation (EU) 2018/1139 on civil aviation. The exclusion depends on that certification. A product used in aviation that has no certification under Regulation (EU) 2018/1139 stays in scope.

Article 2(2)(c) excludes products to which Regulation (EU) 2019/2144 on vehicle type-approval applies. Under that Regulation, vehicle type-approval includes UN Regulation No 155 on cyber security management systems and UN Regulation No 156 on software updates. Commission guidance C(2026) 5252 applies the exclusion also to components designed and constructed exclusively for those vehicles. A generic equivalent sold through channels open to the general public stays in scope.

Article 2(4) excludes equipment that falls within the scope of Directive 2014/90/EU on marine equipment.

These exclusions prevent a second set of cybersecurity rules in sectors that already have their own. Manufacturers in these sectors should record which legal act applies to each product line.

CRA reference:Article 2(2)(c), 2(3) and 2(4)

Excluded Sectors: Military and National Security

Article 2(7) excludes products with digital elements that are developed or modified exclusively for national security or defence purposes. It also excludes products that are specifically designed to process classified information. National security stays the responsibility of each Member State, and the exclusion reflects that limit on EU competence.

The word exclusively decides the result. A product sold to civilian customers and also to defence customers is in scope. A version that the manufacturer modifies exclusively for a defence customer can be outside the CRA, but the civilian version stays in scope.

Manufacturers of such products should record which versions are in scope and make sure that each civilian version complies.

CRA reference:Article 2(7)

Open-Source Software and the CRA

Free and open-source software that is not made available on the market in the course of a commercial activity is outside the CRA. Recital 18 and Recital 19 explain where that line falls. Integration into a commercial product brings the software within the obligations of the manufacturer of that product.

Article 3(14) defines an open-source software steward. A steward is a legal person, other than a manufacturer, that gives systematic support on a sustained basis to the development of specific free and open-source products intended for commercial activities. Article 24 gives stewards a lighter set of obligations. A steward must put in place and document a cybersecurity policy that covers the handling of vulnerabilities. A steward must also cooperate with market surveillance authorities when they ask.

For most commercial software companies that use open-source components, the obligations fall on the manufacturer of the final product. Article 13(5) requires that manufacturer to exercise due diligence when it integrates components from third parties, open-source components included.

CRA reference:Article 3(14), Article 13(5), Article 24, Recital 18, Recital 19

Products Placed on the Market vs. Custom-Built Products

The CRA applies to products 'placed on the market' - meaning made available to third parties through a commercial distribution channel. Custom-built products manufactured for a single customer's specific use, and not made available more broadly, occupy a grey zone that may be addressed in implementing guidance.

Products developed entirely in-house for internal use, with no distribution to third parties, are generally not within scope. However, manufacturers who sell or license products to external customers, even under bespoke contracts, are likely within scope. The key question is whether the product is made available to parties beyond the manufacturer's own organisation.

CRA reference:Article 2(1), Article 3(21)

Are web applications and websites in scope?

Generally not. Commission guidance C(2026) 5252 explains that for software to fall within the CRA it must be provided to a user, obtained by that user, and operated on or as part of an electronic information system on the user's side. Software that executes remotely and is merely accessed by the user does not meet that description, which is typically the case for web applications, including progressive web apps, accessed exclusively through a browser. Websites are not themselves products with digital elements, and enter scope only where they support the functionality of a product, meaning they qualify as remote data processing.

The delivery model decides this rather than the technology. A desktop application built with web technologies but packaged for local installation is a product with digital elements, as is a browser extension and a mobile application downloaded from an app store.

Hardware and the software necessary for it to perform its intended functions form a single product, even where the software is obtained through a separate channel after the hardware was placed on the market. Printer drivers and companion apps for wearables both fall on this side of the line.

Components designed and constructed exclusively for integration into vehicles covered by Regulation (EU) 2019/2144 or Regulation (EU) No 168/2013 are out of scope. Selling a generic equivalent through channels open to the general public brings it back in, whatever the stated intended use.

CRA reference:Article 2(1) and 2(2)(c); Commission guidance C(2026) 5252 points 20 to 25 and 241 to 246

Work through Article 2 for each product in one CRA workspace.

Classify the product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.

Frequently asked

Is SaaS excluded from the CRA?+

Pure SaaS and cloud services - where the software is accessed remotely and no product is placed on the market - are generally excluded. However, hybrid products that combine a physical device with cloud connectivity are in scope. The software component embedded in the device, and any firmware or client software distributed to users, is subject to CRA requirements.

Does the MDR/IVDR exclusion apply to the entire device or only certain components?+

The exclusion applies to the medical device as a whole if it is regulated under MDR or IVDR. General-purpose IT infrastructure or software tools used in hospitals but not classified as medical devices are not automatically excluded - they would need to be assessed under the CRA in the normal way.

Are cybersecurity products like firewalls or antivirus software within scope?+

Yes. Cybersecurity products - including firewalls, antivirus software, intrusion detection systems, and VPNs - are within scope and are classified as important or critical products under Annex III or Annex IV. They face more stringent conformity assessment requirements than default-class products.

What happens when the CRA and another sector regulation both seem to apply?+

The CRA includes lex specialis provisions that defer to sector-specific regulations where they cover the same cybersecurity requirements with equivalent stringency. Article 2 lists the sectors where this applies. For products outside these explicit exclusions, the CRA applies in full even if other regulations also impose some security requirements.

Does the scope include products manufactured outside the EU but sold into the EU?+

Yes. The CRA applies based on where products are placed on the market, not where they are manufactured. A manufacturer outside the EU that sells products in the EU has the same obligations as a manufacturer in the EU. Under Article 18(1) it may appoint an authorised representative established in the EU by a written mandate. The appointment is optional and does not replace the obligations of the manufacturer.

Need a CVD policy for Article 2?

Annex I Part II(5) asks for a coordinated vulnerability disclosure policy. Download a free template.

Browse templates →