The CRA introduces a two-tier system for “important” products with digital elements—Class I and Class II—as defined in Article 7 and detailed in Annex III of the regulation.
Understanding the distinction is crucial because it determines the type of conformity assessment required. In short: Class I allows more flexibility (often self-assessment), while Class II usually requires notified bodies.
Class I: Lower Impact, but Still Important
Class I includes products that:
- Perform security functions, but in a more isolated or user-facing context.
- Are less critical in terms of central control or large-scale impact.
Examples from Annex III, Class I:
- Password managers
- VPN clients
- Smart card readers
- Desktop antivirus software
- Software firewalls for end-user devices
These products might protect a single user or device, but they’re not central to managing entire networks or infrastructures.
Conformity route: In most cases, you can apply internal control procedures as outlined in Article 32(2)(a).
Class II: High-Risk, Central Roles
Class II covers products that:
- Are central to managing, controlling, or securing broader systems.
- Pose a significant cybersecurity risk if compromised (per Article 7(2)).
Examples from Annex III, Class II:
- Operating systems
- Cloud hypervisors
- Identity and access management systems
- Network management controllers
- Security Information and Event Management (SIEM) systems
- Virtual private network (VPN) gateways used in enterprises
These tools usually affect multiple systems, users, or services. A failure here could cascade through entire infrastructures.
Conformity route: Requires a more rigorous assessment, such as:
- Type examination + internal production control (Article 32(2)(b)), or
- Full quality assurance procedures (Article 32(3)).
How to Determine Your Class
Ask yourself:
- Does your product match a listed category in Annex III?
- Does it perform a core function in cybersecurity (access control, intrusion detection, endpoint protection)?
- Could it be used in a way that impacts multiple other systems if compromised?
If you’re unsure or fall into a grey area, err on the side of Class II. It’s safer from a regulatory standpoint and aligns with the precautionary approach the Commission takes in Article 7(3).
Need help deciding?
Drop a short description of your product here and we can figure it out together. This is a critical step for selecting your conformity path, and getting it right upfront saves a lot of headaches later.