Article 3

Definitions: Key Terms in the Cyber Resilience Act

Article 3 contains the statutory definitions that underpin the entire Cyber Resilience Act. The most consequential definition is 'product with digital elements' — any hardware or software product capable of connecting, directly or indirectly, to a device or network. Other defined terms establish who bears obligations (manufacturer, importer, distributor, authorised representative) and what types of activity are regulated (placing on the market, making available, substantial modification). Correctly applying these definitions is the essential first step in CRA compliance planning.

Effective: December 2027Applies to: Manufacturers, importers, and distributors of products with digital elements sold in the EU marketLast reviewed: 26 October 2026Verified against: the final text of Regulation (EU) 2024/2847
Source: Regulation (EU) 2024/2847, Article 3, official text on EUR-Lex

What Is a 'Product with Digital Elements'?

The CRA defines a product with digital elements as any software or hardware product (and its remote data processing solutions) that:

  1. Can connect - directly or indirectly - to another device or network
  2. Is placed on the EU market (sold to EU customers) after the application date
  • Physical hardware devices with embedded software (IoT devices, routers, industrial controllers)
  • Standalone software applications (both desktop and mobile)
  • Operating systems and firmware
  • Software components sold as part of a larger product

Key test: Does the product have any form of network connectivity, even indirect? If yes, it is likely in scope.

CRA reference:Article 3(1), Recital 13

What Is Excluded from CRA Scope?

Article 3 gives definitions only. The exclusions from scope are in Article 2.

  • Medical devices. Article 2(2), points (a) and (b), exclude products to which Regulation (EU) 2017/745 or Regulation (EU) 2017/746 applies.
  • Vehicles. Article 2(2), point (c), excludes products to which Regulation (EU) 2019/2144 on vehicle type-approval applies.
  • Civil aviation. Article 2(3) excludes products certified in accordance with Regulation (EU) 2018/1139.
  • Marine equipment. Article 2(4) excludes equipment within the scope of Directive 2014/90/EU.
  • Spare parts. Article 2(6) excludes spare parts that replace identical components and are manufactured to the same specifications.
  • National security and defence. Article 2(7) excludes products developed or modified exclusively for national security or defence purposes, and products specifically designed to process classified information.

A product near one of these sectors stays in scope when the sector legal act does not apply to it. For example, a fitness tracker that is not a medical device is in scope of the CRA.

CRA reference:Article 2(2) to (4), (6) and (7)

The SaaS and Cloud Services Question

Pure Software as a Service (SaaS) and cloud services are generally not covered by the CRA. The CRA focuses on products placed on the market - i.e., products that are downloaded, installed, or shipped as physical goods.

  • Software that is downloaded and installed on a device (mobile apps, desktop applications) is in scope.
  • Hardware products that rely on cloud connectivity for their primary function are in scope (the hardware product, not the cloud service itself).
  • If a vendor offers both a downloadable product and a cloud-hosted version, the downloadable product is likely in scope.

This distinction is important for software vendors who offer both SaaS and on-premise deployment options.

CRA reference:Article 3, Recital 12

Who Has Obligations Under the CRA?

The CRA distinguishes between three roles in the supply chain:

  1. Manufacturers - Companies that design, develop, and produce products, or have them designed/produced and sell them under their own name or trademark. Manufacturers bear the primary compliance obligations.
  1. Importers - Companies that bring non-EU products into the EU market. Importers must verify manufacturer compliance and may bear liability if a manufacturer is unreachable.
  1. Distributors - Companies that make products available on the EU market without placing them on the market themselves. Distributors have lighter obligations but must verify that products bear proper CE marking.

For global manufacturers with EU customers, the manufacturer obligations apply regardless of where the manufacturer is based.

CRA reference:Article 3, Articles 13, 19 and 20

How the Commission guidance reads the key definitions

Commission guidance C(2026) 5252 works through several Article 3 definitions in detail.

Remote data processing under Article 3(2) reduces to two cumulative questions. Would its absence prevent the product performing one of its functions, which is not limited to the core functionality or the intended purpose, and was the software designed and developed by the manufacturer or under its responsibility, meaning tailor-made to its own designs and specifications. Both yes makes the module part of the product. Your own software on a third-party IaaS or PaaS qualifies. A third-party SaaS application you integrate does not, and is treated as a component attracting Article 13(5) due diligence. Who operates the solution is irrelevant, so on-premises and private cloud qualify on the same terms as public cloud.

Substantial modification under Article 3(30) gains a four-factor test at guidance point 110. Does the change introduce new threat vectors, enable new attack scenarios, change the likelihood of previously identified attack scenarios, or change their impact. The scale of the change is expressly not part of the test.

Free and open-source software under Article 3(48) requires two things cumulatively. A licence granting the full set of rights, and source code that is openly shared. Software under a free licence whose source is shared only with paying customers or a limited group does not qualify.

CRA reference:Article 3(2), 3(30) and 3(48); Commission guidance C(2026) 5252 points 44 to 46, 110 and 184 to 202

Work through Article 3 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

Does the CRA apply to open-source software?+

Open-source software that is not commercialised is generally outside CRA scope. 'Commercialised' means the software is provided in the course of a commercial activity - including free software that supports a paid service or subscription. Open-source stewards and foundations are subject to lighter obligations under the CRA compared to commercial manufacturers.

Does the CRA apply to B2B software?+

Yes. The CRA applies to all products placed on the EU market regardless of whether they are sold to businesses or consumers. There is no B2B exemption.

If my product is made outside the EU, does the CRA apply?+

Yes - if you sell or make your product available to EU customers, the CRA applies to you regardless of where you are headquartered or where the product is manufactured. The CRA is a market access requirement, not a jurisdictional one.

What about legacy products sold before September 2026?+

Products placed on the market before the CRA application date are not immediately subject to its requirements. However, products substantially modified after that date, or products that continue to be actively sold after that date under new production runs, will generally need to comply.

Need a CVD policy for Article 3?

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

Browse templates →