SDG data protection blog

Laws & regulationIT security

CRA Conformity Assessment: Product Classes and Modules

11 November 2026 by Sebastian Baier · Reading time approx. 9 minutes

Which conformity assessment procedure a product undergoes under the Cyber Resilience Act depends on its class (Art. 32 of Regulation (EU) 2024/2847): the manufacturer assesses default products itself (module A), and important products of class I only if it fully applies harmonised standards, common specifications or a European cybersecurity certification scheme. Class II requires a notified body or a European certificate; critical products primarily require a European certificate. The requirements themselves are the same for all classes. The conformity assessment must be completed for products placed on the market from 11 December 2027.

This article shows how to classify your product, which modules exist and how to plan the route to CE marking. An overview of the CRA can be found on the page Cyber Resilience Act consulting.

Step 1: Classify the product

The class is determined by the core functionality of the product (Art. 7 CRA). A product that merely integrates a browser or a VPN component does not automatically become an important product itself. The categories are listed in Annex III (important products, classes I and II) and Annex IV (critical products). The Commission has set out their technical description in Implementing Regulation (EU) 2025/2392. These descriptions are suitable as an assessment grid.

Class Basis Examples
Default product not listed in Annex III or IV the majority of products with digital elements
Important, class I Annex III class I including password managers, browsers, VPN products, operating systems, routers, modems and switches, smart home products with security functionalities
Important, class II Annex III class II including firewalls, intrusion detection and prevention systems, hypervisors and container runtime systems, tamper-resistant microprocessors
Critical Annex IV including hardware devices with security boxes, smart meter gateways, smartcards and secure elements

Document the classification with a justification. It is the basis for everything else and one of the first questions in an inspection by the authorities.

The procedures under Art. 32

Class Permitted procedures Notified body required?
Default product module A, B and C, H or European cybersecurity certification scheme (para. 1) no, for module A
Important, class I module A only if harmonised standards, common specifications or a European cybersecurity certification scheme at assurance level at least "substantial" are fully applied; otherwise module B and C or H (para. 2) only without fully applied standards or a certificate
Important, class II module B and C, module H or European cybersecurity certification scheme at assurance level at least "substantial" (para. 3) yes, unless there is a certificate
Critical primarily a European cybersecurity certification scheme under Art. 8(1); if its conditions are not met, the same procedures as for class II (para. 4) yes

Special rule for open source: for free and open-source software in the categories of Annex III, the procedure under para. 1, and therefore also module A, is permitted if the technical documentation is made available to the public (Art. 32(5)).

Small companies: the specific interests and needs of microenterprises and small and medium-sized enterprises, including start-ups, must be taken into account when setting the fees for conformity assessment, and the fees must be reduced proportionately (Art. 32(6)).

The modules at a glance

Module What happens Who assesses
A: internal control The manufacturer ensures conformity itself and draws up the technical documentation and the EU declaration of conformity. the manufacturer only
B: EU-type examination A notified body examines the technical design and the vulnerability handling processes and issues an EU-type examination certificate. notified body
C: conformity to type based on internal production control The manufacturer ensures that the products conform to the examined type. Combined with module B. manufacturer
H: conformity based on full quality assurance A notified body assesses and monitors the manufacturer's quality system for design, development, production and vulnerability handling. notified body

B and C is a good fit if you have few products with clearly delimited versions. H tends to pay off for manufacturers with many products and established quality management, because the system is assessed rather than each individual type. For module H, the BSI (Federal Office for Information Security) has published Technical Guideline TR-03183-H, currently in version 1.1.0.

Harmonised standards and notified bodies

Harmonised standards are the key for class I: only those who apply them in full may carry out the assessment without a notified body. They also give rise to the presumption that the requirements they cover are met. They are being developed by CEN, CENELEC and ETSI on behalf of the Commission: horizontal standards in the EN 40000 series and product-specific standards. To our knowledge, none of these standards had been published in the Official Journal of the EU at the time of going to press, so they do not yet give rise to a presumption of conformity. Check the status regularly.

Notified bodies (conformity assessment bodies) must be notified for the CRA. The provisions on this have applied since 11 June 2026. In Germany, the BSI is to become the notifying authority under the CRA-Durchführungsgesetz (German CRA implementation act). Because many manufacturers will need appointments at the same time before December 2027, bottlenecks are to be expected. Enquire early.

Practical consequence

As long as harmonised standards are lacking, manufacturers of class I products should plan with a notified body as a precaution.

Technical documentation, declaration of conformity and CE

Regardless of the module, every conformity assessment includes:

Element Basis Content
Technical documentation Art. 31, Annex VII description of the product, design and development, vulnerability handling processes including the SBOM, cybersecurity risk assessment, support period, applied standards, test reports
EU declaration of conformity Art. 28, Annex V statement by the manufacturer that the requirements are fulfilled; a simplified version in accordance with Annex VI is possible
CE marking Art. 30 on the product; for software, on the EU declaration of conformity or the accompanying website

Technical documentation and the declaration of conformity must be kept for at least ten years or for the support period, whichever is longer. How the SBOM fits into the documentation is explained in the article SBOM under the CRA.

Roadmap to December 2027

  1. Record the product portfolio Classify each product with a justification.
  2. Determine the procedure Module A, B and C, H or certificate, depending on the class and the status of standards.
  3. Gap analysis against Annex I Check for each product line which requirements are still missing.
  4. Select and contact a notified body Early on, if it is foreseeable that you will need one.
  5. Implement the requirements Embed secure development and vulnerability handling.
  6. Build the technical documentation Ideally in parallel with development.
  7. Carry out the assessment Draw up the declaration of conformity, affix the CE marking.

For procedures involving a notified body, allow sufficient lead time. The manufacturer obligations in detail are described in the article CRA: obligations for manufacturers.

How SDG supports you

We advise manufacturers and support implementation. We do not test or certify products ourselves; that is the task of the notified bodies.

  • Classification of your products on the basis of Annexes III and IV and Implementing Regulation (EU) 2025/2392
  • Recommendation on the procedure, taking into account your product portfolio and the status of standards
  • Gap analysis against Annex I and support with implementation
  • Structuring the technical documentation and preparing for the assessment by a notified body
  • Linking with ISO 27001 if you want to use a management system for module H: ISO 27001 consulting

Frequently asked questions about CRA conformity assessment

Which conformity assessment procedure applies to my product?

That depends on the class. The manufacturer assesses default products itself (module A). Important products of class I only with fully applied harmonised standards, common specifications or a European certificate, otherwise with a notified body. Class II requires a notified body or a European certificate; critical products primarily a European certificate.

What determines the product class?

The core functionality of the product. The decisive factor is the categories in Annexes III and IV of the Regulation, whose technical description is set out in Implementing Regulation (EU) 2025/2392. Integrated components do not automatically make a product an important product.

When do I need a notified body?

For important products of class II without a European certificate, for critical products where no suitable certification scheme applies, and for class I where harmonised standards, common specifications or certification schemes are lacking or are not fully applied.

What is the difference between module B and C and module H?

With B and C, a notified body examines the type of the product and the manufacturer ensures conformity in production. With H, the notified body assesses and monitors the manufacturer's entire quality system. H tends to pay off where there are many products.

Does a different procedure apply to open-source software?

For free and open-source software in the categories of Annex III, module A is also permitted if the technical documentation is made available to the public (Art. 32(5)).

How do I affix the CE marking to software?

For software, the CE marking can be affixed to the EU declaration of conformity or to the website accompanying the product (Art. 30).

By when must the conformity assessment be completed?

For products placed on the market from 11 December 2027. For procedures involving a notified body, you should start considerably earlier because bottlenecks are foreseeable.


Sources: Regulation (EU) 2024/2847 (Cyber Resilience Act), Implementing Regulation (EU) 2025/2392, BSI TR-03183

Note: This article provides general information and does not replace legal advice in individual cases.