Article 7

Important Products with Digital Elements - Annex III Classification

Article 7 makes a product with digital elements important when its core functionality matches a product category in Annex III. Annex III divides those categories into Class I, with 19 categories, and Class II, with 4. A Class I product can use self-assessment only when the manufacturer fully applies a harmonised standard, a common specification or a European cybersecurity certification scheme. A Class II product always needs a notified body or a European cybersecurity certification scheme specified under Article 27(9).

Effective: December 2027Applies to: Manufacturers of products listed in Annex III to the CRALast reviewed: 26 October 2026Verified against: the final text of Regulation (EU) 2024/2847
Source: Regulation (EU) 2024/2847, Article 7, official text on EUR-Lex

What Makes a Product 'Important' Under Article 7

Article 7(1) makes a product important when it has the core functionality of a product category in Annex III. Article 7(2) sets two criteria, and each Annex III category meets at least one of them:

  1. The product primarily performs functions critical to the cybersecurity of other products, networks or services. The examples in the text are securing authentication and access, intrusion prevention and detection, end-point security and network protection.
  1. The product performs a function with a significant risk of adverse effects. The risk is in its intensity and its ability to disrupt, control or cause damage to a large number of other products, or to the health, security or safety of its users through direct manipulation. The examples in the text are central system functions such as network management, configuration control, virtualisation and processing of personal data.

The criteria explain why a category is in Annex III. They do not classify a product on their own. Only a core functionality that matches a category in Annex III makes a product important. Industrial control systems, robots and smart grid equipment are therefore default class unless their core functionality matches a listed category. The Commission may update Annex III by delegated act (Article 7(3)).

CRA reference:Article 7(1), Article 7(2)

Class I vs Class II: The Two Tiers

Annex III divides important products into two classes with different conformity assessment routes.

  • Identity management systems and privileged access management software and hardware, including authentication and access control readers
  • Standalone and embedded browsers
  • Password managers
  • Products with the function of a virtual private network (VPN)
  • Network management systems
  • Operating systems
  • Routers, modems intended for the connection to the internet, and switches
  • Microcontrollers with security-related functionalities
  • Smart home products with security functionalities, such as smart door locks, security cameras, baby monitoring systems and alarm systems
  • Hypervisors and container runtime systems that support virtualised execution of operating systems and similar environments
  • Firewalls, intrusion detection and prevention systems
  • Tamper-resistant microprocessors
  • Tamper-resistant microcontrollers

Hardware devices with security boxes, smart meter gateways, and smartcards and secure elements are critical products, listed in Annex IV. Class II carries the highest conformity assessment burden short of critical products.

CRA reference:Annex III, Annex IV

Conformity Assessment for Class I Products

A Class I product can use Module A internal control only when the manufacturer fully applies a harmonised standard, a common specification or a European cybersecurity certification scheme at assurance level at least substantial (Article 32(2)). Otherwise the manufacturer chooses one of two routes:

EU-type examination (Module B) followed by conformity to type (Module C). A notified body examines the technical design and development of the product and the vulnerability handling processes, and issues an EU-type examination certificate. Production then follows internal control against the approved type.

Full quality assurance (Module H). A notified body assesses the manufacturer's quality system for design, development, production and vulnerability handling. This route suits manufacturers with several products.

No CRA harmonised standard is cited in the Official Journal yet, so today a Class I product needs one of these notified body routes. The manufacturer references the notified body's certificate or approval in the EU declaration of conformity and keeps responsibility for the product's compliance.

CRA reference:Article 32(2), Annex VIII

Conformity Assessment for Class II Products

Module A is never open to a Class II product. The manufacturer uses one of the routes in Article 32(3). They are EU-type examination (Module B) followed by conformity to type (Module C), full quality assurance (Module H), or a European cybersecurity certification scheme at assurance level at least substantial, where one is available and applicable.

  • Module B involves the notified body examining the product design and, where appropriate, representative production samples against the essential requirements and any applicable harmonised standards.
  • Module C confirms that production units conform to the approved type.
  • Module H is an alternative in which the notified body assesses and certifies the manufacturer's whole quality system, including development, production and testing.

Class II manufacturers should engage with notified bodies early, as assessment timelines for complex products can be 6–18 months.

CRA reference:Article 32(3), Annex VIII

The Commission's Power to Update Annex III

Article 7 grants the European Commission the power to amend Annex III by delegated act, adding or removing product categories as the threat landscape and technology evolve. When the Commission proposes to add a product category, it must provide a minimum transitional period of 12 months before the new classification takes effect, giving affected manufacturers time to adapt their conformity assessment processes.

Manufacturers of products in adjacent categories — or of products whose security properties are becoming more critical — should monitor Commission delegated acts under Article 7. ENISA publishes analysis of product category risk profiles that may inform future Annex III amendments.

CRA reference:Article 7(3)

What counts as the 'core functionality'?

Core functionality is not defined in the Regulation. Commission guidance C(2026) 5252 describes it as the product's main features and technical capabilities, without which it would not be able to meet its intended purpose, assessed in light of the information the manufacturer supplies in the instructions for use, in promotional and sales materials, and in the technical documentation.

Four rules follow. A product has only one core functionality for the purposes of determining the conformity assessment regime, and it must be identified in the technical documentation. Functions additional to the core functionality do not change the classification. Merely integrating an important or critical product does not make the host product important or critical, so a smartphone containing an operating system does not have the core functionality of an operating system. And where a product's core functionality substantially exceeds or substantially falls short of a category, it does not belong to it. Security orchestration, automation and response software generally exceeds the SIEM category because incident response is core to it, while a log collection and visualisation tool that performs no correlation falls short of it.

Modules of an integrated product that the manufacturer also makes available separately, for separate purchase, licensing or subscription, are standalone products classified on their own core functionality.

A manufacturer may not misrepresent core functionality to escape a more stringent regime. Clear inconsistency between promotional materials, instructions for use and the technical documentation is the signal, and non-compliance with Article 32 can attract administrative fines under Article 64(3).

CRA reference:Article 7(1) and 8(1); Commission guidance C(2026) 5252 points 136 to 146

Work through Article 7 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 my product automatically Class I or Class II, or do I have to self-classify?+

You must assess whether your product matches the descriptions in Annex III. If it does, you must apply the appropriate conformity assessment procedure. There is no central classification authority — the manufacturer is responsible for self-identifying Annex III status and documenting the rationale. If your product could be argued either way, seek legal or conformity assessment advice and document your decision.

What if I integrate an Annex III product as a component into my product?+

Integrating an Annex III product as a component does not automatically make the integrating product an Annex III product. However, you must ensure that the Annex III component you source carries a valid CE marking and Declaration of Conformity from its manufacturer before integration. You remain responsible for the overall compliance of the final product.

Are there any notified bodies already designated for CRA Annex III assessments?+

Member states designate notified bodies through their national notifying authorities. As of the CRA's application date, the European Commission maintains a NANDO (New Approach Notified and Designated Organisations) database listing CRA-designated notified bodies. Early engagement with notified bodies is strongly recommended for Class I and Class II manufacturers, as assessment capacity may be limited initially.

Can a product move from Class I to Class II over time?+

If the Commission amends Annex III to reclassify a product from Class I to Class II by delegated act, the delegated act provides, where appropriate, a minimum transitional period of 12 months (Article 7(3)). Manufacturers of products already on the market at the time of reclassification may have additional time to bring products into compliance with the new classification's conformity assessment requirements. Check the specific delegated act for transitional provisions.

Need a CVD policy for Article 7?

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

Browse templates →