Under the Cyber Resilience Act, whether you can sign your own declaration of conformity or must pay a notified body to assess your product depends on where your product sits in the regulation's three-tier classification: a default product can usually self-assess, an Annex III "important" product can sometimes self-assess and sometimes cannot, and an Annex IV "critical" product is built around third-party involvement from the start. This guide walks through Article 32's conformity assessment routes and how they connect to that classification, as covered by consistent secondary legal analysis of the regulation.
The article and annex references below were checked on 10 November 2026 against the Official Journal text of Regulation (EU) 2024/2847, the Commission's CRA conformity assessment page and the Commission's FAQs on the CRA (version 1.4). The FAQ answers further down predate that check and keep their original wording.
Key takeaways
- Module A — internal control (self-assessment).
- In Annex VIII. Article 32 refers to "Annex VIII" for every module, and the Official Journal text splits it into four parts.
- Your product's tier under Annex III and IV decides which Article 32 routes are open.
- The work differs mainly in who examines what and how often.
What is a conformity assessment procedure?
A conformity assessment procedure is how a manufacturer demonstrates — to itself, to a market surveillance authority, or to a notified body — that a product with digital elements meets the Annex I essential cybersecurity requirements before it is placed on the market. It is separate from the requirements themselves: see CRA Annex I explained for what must actually be built. Article 32(1) of the Regulation lists four routes; which of them you may use depends on the product's classification:
- Module A — internal control (self-assessment). The manufacturer assesses its own product's conformity, draws up the technical documentation, and signs the EU declaration of conformity, without a notified body.
- Modules B + C together — EU-type examination plus internal production control. A notified body examines the technical design and the vulnerability handling processes, including specimens of critical parts (module B); the manufacturer then makes every unit conform to that approved type (module C). Article 32 always pairs B with C.
- Module H — full quality assurance. A notified body assesses and audits the manufacturer's quality system for design, development, testing and vulnerability handling, rather than a single product type.
- A European cybersecurity certification scheme, where one has been adopted under the Cybersecurity Act (Regulation (EU) 2019/881) and specified for the CRA by delegated act under Article 27(9) — the EUCC scheme is the first such scheme to exist, though it was not built specifically for the CRA.
Whatever the route, the manufacturer signs the declaration and carries the responsibility (Article 28(4)).
Where does the module structure live in the regulation?
In Annex VIII. Article 32 refers to "Annex VIII" for every module, and the Official Journal text splits it into four parts. Some older summaries cite "Annex VI" for the modules; in the adopted text Annex VI is the simplified declaration of conformity.
| Annex | What it contains |
|---|---|
| Annex V | Model EU declaration of conformity |
| Annex VI | Simplified EU declaration of conformity (one sentence plus a web address) |
| Annex VII | Technical documentation |
| Annex VIII Part I | Module A, internal control |
| Annex VIII Part II | Module B, EU-type examination |
| Annex VIII Part III | Module C, conformity to type based on internal production control |
| Annex VIII Part IV | Module H, full quality assurance |
How does classification decide your route?
Your product's tier under Annex III and IV decides which Article 32 routes are open. The Commission's conformity assessment page (last update 31 July 2026) gives memory chips, mobile apps, smart speakers and computer games as default-category examples, and smart cards, secure elements and smart meter gateways as critical examples.
| Tier | Assessment routes available | Can you self-assess (Module A)? |
|---|---|---|
| Default (not listed in Annex III or IV) | Module A, or Modules B+C, or Module H, or a certification scheme — manufacturer's choice | Yes, always an option |
| Annex III important, Class I (e.g. browsers, password managers, VPN products, routers/modems/switches, smart home security devices) | Module A only if harmonised standards, common specifications, or a certification scheme at assurance level at least "substantial" have been fully applied to the relevant requirements; otherwise Modules B+C or Module H for the requirements not covered (Article 32(2)) | Conditional — depends on standards coverage |
| Annex III important, Class II (e.g. hypervisors, firewalls/IDS/IPS, tamper-resistant microprocessors/microcontrollers) | Modules B+C, Module H, or a certification scheme at assurance level at least "substantial" (Article 32(3)) | No — third-party involvement always required |
| Annex IV critical (e.g. hardware security modules, smart meter gateways, smartcards/secure elements) | A European cybersecurity certification scheme where the Commission has required one by delegated act under Article 8(1); otherwise the Class II routes (Article 32(4)) | No |
Two qualifications from Article 32 itself:
- Free and open-source software carve-out. Under Article 32(5), an Annex III important product (Class I or II) that is free and open-source software may use any Article 32(1) route, including Module A, if its technical documentation is public when the product is placed on the market. The carve-out does not cover Annex IV critical products.
- SME fees. Article 32(6) requires conformity assessment fees to take account of the interests of micro, small and medium-sized enterprises and to be reduced proportionately. It sets no fixed percentage. Article 33(5) separately lets micro and small enterprises use a simplified technical documentation form, which notified bodies must accept once the Commission has adopted it by implementing act.
What does each route involve in practice?
The work differs mainly in who examines what and how often. This summary follows Annex VIII and the Commission's FAQs on the CRA, entries 6.1 to 6.3.
| Step | Module A | Modules B + C | Module H |
|---|---|---|---|
| Who examines | Manufacturer only | One notified body of your choice examines the type | One notified body assesses the quality system |
| What is examined | Your own tests and the Annex VII documentation | Technical documentation, supporting evidence and specimens of critical parts; tests by the body or a lab | Quality system documentation, technical documentation for one model per product category, visit to your premises |
| Output | Declaration of conformity on your sole responsibility | EU-type examination certificate, valid for the period the body sets | Approved quality system, with an audit report |
| Ongoing | Keep production and vulnerability handling compliant | Body runs periodic audits of Part II vulnerability handling | Body runs periodic surveillance audits |
| CE marking | CE only | CE only | CE followed by the body's identification number (Article 30(4)) |
| Keep for authorities | Declaration + documentation for 10 years or the support period, whichever is longer | Same, plus the certificate and its additions | Same, plus quality system records and the body's decisions |
Under modules B and H, documentation and correspondence must be in an official language of the notified body's Member State or one it accepts (Article 31(4)).
Module B+C or module H: which fits a device maker?
B+C examines one product type at a time; H approves a system that then covers a catalogue. The Commission FAQ (6.3) says module H suits manufacturers that place many product types on the market or update products often, because new or substantially modified products are added to an approved system with a narrower re-assessment. Some practical signals:
- One or two product types with stable firmware: B+C is usually simpler; the body examines the type and you run production.
- A family of models sharing a firmware platform, with frequent releases: H can avoid a fresh type examination per model, but needs a documented quality system covering design, testing and vulnerability handling.
- An existing ISO 9001 system: a starting point for H, not a shortcut. The FAQ notes that ISO 9000 accreditation alone does not entitle you to module H; a CRA notified body still has to approve the system.
What happens after a firmware update or a change?
Under self-assessment you update the technical documentation and, where needed, the declaration. Under a notified-body route there are extra duties, set out in Annex VIII:
Inform the bodyUnder module B, tell the body that holds the certificate about every change to the approved type or the vulnerability handling processes that may affect conformity; such changes need an addition to the certificate (Part II, point 7). Expect the body to watch the state of the artIf it concludes the approved type may no longer comply, it informs you (same point). Expect periodic auditsof your vulnerability handling under module B (point 8) and of the quality system under module H (Part IV, point 4.3). Treat substantial modifications as a new assessmentThe FAQ (6.2) says a substantial modification needs a new assessment by the same or a different body; changes that do not affect compliance do not. Under module H, report intended changes to the quality systembefore you make them (Part IV, point 3.5).
Routine security patches that leave the approved design intact are the normal case, but the classification of each change should be written down.
Where do you find a notified body, and when can they start?
The CRA's rules on notifying conformity assessment bodies (Chapter IV, Articles 35 to 51) have applied since 11 June 2026 (Article 71(2)); the product obligations apply from 11 December 2027. Bodies are assessed and notified by their Member State and then listed in the Commission's NANDO database. When we read the Commission's conformity assessment page on 10 November 2026, it said NANDO would list CRA notified bodies "once available", so check NANDO for bodies notified under Regulation (EU) 2024/2847 before you plan. ENISA's Technical Competence Requirements for CRA Notified Bodies (4 June 2026) describes the auditor and evaluator skills bodies are expected to show, which is useful when you compare candidates.
Worked example: which route for a home router line?
The company below is hypothetical and synthetic, not a customer case. It sells four home Wi-Fi router models on one firmware platform with monthly releases, plus a Wi-Fi smart plug.
ClassifyThe routers match Annex III Class I point 12 ("routers, modems intended for the connection to the internet, and switches"). The smart plug's core function is switching power, not a listed category, so it is default. Smart plugModule A: risk assessment, tests, Annex VII documentation, declaration and CE marking. Routers: check standards coverageOn 10 November 2026 no CRA harmonised standard was cited in the Official Journal (see CRA harmonised standards). If that is still true for any relevant requirement when the routers go on sale, Article 32(2) sends those requirements to B+C or H. Pick the moduleFour models on one platform with monthly releases point towards module H; a single model with stable firmware would point towards B+C. Line up a bodyCheck NANDO, ask about lead times, and agree the language for documentation. Plan for updatesWrite a change classification rule (security patch, feature change, substantial modification) and a notification step to the body. Mark and declareUnder module H, the CE marking carries the body's number; the declaration follows Annex V, and the product may ship with the one-sentence Annex VI version that links to it (Article 13(20)).
If the routers hold an EU-type examination certificate for cybersecurity under the Radio Equipment Directive's delegated act, Article 69(1) keeps such certificates valid until 11 June 2028, unless they expire earlier.
What should a device maker do now?
Classify the product firstWork out whether it falls under Annex III or Annex IV before planning the route — see CRA Annex III and IV: important and critical products explained and the technical descriptions in Implementing Regulation (EU) 2025/2392. If you land in default or Class I, check harmonised-standards coverage earlyFor default products, Module A is available regardless; for Class I, self-assessment depends on fully applying harmonised standards, common specifications or a "substantial" certification scheme, so do not assume it stays available. If you land in Class II or Annex IV, start notified-body or certification-scheme conversations nowThird-party capacity and scheme timelines are a planning constraint, not paperwork for the end. Keep the technical documentation current regardless of routeModule A, Modules B+C and Module H all rest on accurate Annex VII documentation — a notified body will review it, and a market surveillance authority can request it even under self-assessment. Remember that legacy types are coveredThe CRA applies to each unit placed on the market from 11 December 2027, so a model first sold years earlier still needs an assessment for new units (FAQ 6.4 and 7.2).
For a comparison of the modules from the selection angle, see EU CRA conformity assessment modules; for the paperwork, see declaration of conformity and technical documentation.
What are the common pitfalls?
- Assuming Class I means self-assessment. Without fully applied harmonised standards, common specifications or a "substantial" certificate, Article 32(2) requires a notified body.
- Treating a draft standard as covering you. Presumption of conformity starts only with an Official Journal reference (Article 27(1)).
- Lodging with several bodies. Modules B and H require a declaration that the application was not lodged with any other body.
- Forgetting post-certificate duties. Changes that may affect conformity go back to the body under module B.
- Classifying by component. A secure element inside a device does not by itself make the device critical; the device's core functionality decides (Article 7(1)).
Where does AI fit: evidence, not the classification decision?
Regardless of which Article 32 route applies, a self-assessment or a notified body checks the same evidence of component-level risk. SoftWSP's firmware scan extracts the SBOM as CycloneDX 1.6 JSON, matches components against NVD, CISA KEV, FIRST EPSS and CISA CSAF ICS advisories, and has AI draft a plain-language report with a prioritised fix list, each line citing its source, for an engineer to confirm before it goes into the technical documentation a Module A self-assessment or a notified body's Module B/H review will examine. AI does not decide whether a product needs third-party assessment and does not invent a finding — that classification call stays with the manufacturer and, where required, the notified body.
SoftWSP's firmware security work helps you work out where your product sits under Annex III/IV and what evidence a self-assessment or a notified body will expect to see: see device firmware security. For the underlying essential requirements any route has to demonstrate, see CRA Annex I explained, and for the day-to-day compliance tasks, see the CRA checklist for device makers. Back to the Cyber Resilience Act hub.
This guide is general information, not legal advice, and summarises Regulation (EU) 2024/2847 Article 32 and Annex VIII; confirm against the current official text before relying on it.
Put this guide to work
Frequently asked questions
What is a CRA conformity assessment procedure?
It is the process Article 32 of Regulation (EU) 2024/2847 requires a manufacturer to carry out, or have carried out, before placing a product with digital elements on the market, to demonstrate that the product meets the Annex I essential cybersecurity requirements. Per corroborated secondary legal analysis, the available procedures are internal control (Module A, self-assessment), EU-type examination combined with internal production control (Modules B+C, via a notified body), full quality assurance (Module H, via a notified body), and, where one exists, a European cybersecurity certification scheme.
Can every manufacturer just self-assess under Module A?
No. Module A self-assessment is the default route only for products that are not listed in Annex III or Annex IV. Per secondary analysis of Article 32, Annex III 'important' Class I products can usually still self-assess, but only where the manufacturer has fully applied harmonised standards, common specifications, or a cybersecurity certification scheme at assurance level at least 'substantial' for the relevant essential requirements; otherwise Class I products need third-party involvement too.
Which products definitely need a notified body?
Per secondary analysis, Annex III Class II important products (such as hypervisors, firewalls/IDS/IPS, and tamper-resistant microprocessors or microcontrollers) must always go through third-party assessment: EU-type examination plus internal production control, full quality assurance, or certification at 'substantial' level — self-assessment is not an option for this class. Annex IV critical products face the strictest route, built primarily around a European cybersecurity certification scheme where the Commission has made one mandatory, falling back to the Class II third-party procedures where no scheme is available yet.
Is the module structure in 'Annex VI' of the CRA?
Not in the final adopted text. Several independent secondary sources — including a CRA article-by-article reference site and a legal-tracker summary of Article 32 — consistently place the Module A/B/C/H conformity assessment procedures in Annex VIII of Regulation (EU) 2024/2847, not Annex VI. Those same sources note that an early 2022 Commission proposal did number this material as 'Annex VI,' and that in the final text Annex VI instead holds the model EU declaration of conformity. The Annex VIII numbering here is secondary-source-corroborated; the official Official Journal text is the authoritative source to check before citing it in a compliance submission.
Does open-source software get a self-assessment exception even for important products?
Per secondary analysis of Article 32(5), free and open-source software that falls under an Annex III important-product category can still use the standard self-assessment procedure if its technical documentation is made publicly available when the product is placed on the market — an exception that does not extend to Annex IV critical products or to closed-source important products outside that carve-out.
Sources
- Regulation (EU) 2024/2847 (Cyber Resilience Act), Article 32 and Annexes III, IV and VIII, Official Journal text, EUR-Lex
- European Commission: Cyber Resilience Act, summary of the legal text
- Springlex: Cyber Resilience Act, Article 32 — Conformity assessment procedures for products with digital elements
- Acquislaw: Cyber Resilience Act, Article 32 — full text, verified
- cvdportal: CRA Annex VIII — Conformity Assessment Procedures Explained
- European Commission: Cyber Resilience Act – Conformity assessment (last update 31 July 2026)
- European Commission: FAQs on the Cyber Resilience Act, version 1.4 (4 September 2026)
- European Commission: NANDO notified bodies database
- ENISA: Technical Competence Requirements for CRA Notified Bodies (4 June 2026)
About this guide
SoftWSP Regulation Desk
Covers the Cyber Resilience Act cluster: 34 guides.

In this cluster
Questions about this page?
