CRA conformity assessment: self-assessment or notified body?
Last verified: 2026-11-21.
Information, not legal advice. Our reading of the official sources, not reviewed by a lawyer. You decide how the CRA applies to your product; for an opinion you can rely on, ask a lawyer; for a third-party conformity assessment, a notified body. This guide helps you work with the EU Cyber Resilience Act (Regulation (EU) 2024/2847) but does not certify, assess or guarantee the compliance of any product. You remain responsible for your product's conformity assessment, CE marking and reporting. Last verified against official sources: 2026-11-21.
Short answer
- Before placing a product on the market, the manufacturer carries out a conformity assessment, or has it carried out, to show that the product and its processes meet the essential cybersecurity requirements in Annex I, using a procedure listed in Article 32. These rules apply from 11 December 2027 (CRA Art. 13(12), 32(1), 71(2)).
- Self-assessment means the internal control procedure (module A). It is open to products outside Annexes III and IV, to important Class I products only where harmonised standards, common specifications or a European cybersecurity certification scheme at assurance level at least "substantial" are applied in full, and to free and open-source software in an Annex III category whose technical documentation is public (CRA Art. 32(1)–(2), (5); Guidance, point 137).
- A notified body takes part in EU-type examination followed by conformity to type (modules B + C) and in full quality assurance (module H). Class II products need one of these or a certification scheme; critical products need a European cybersecurity certificate where a delegated act under Article 8(1) requires one, and otherwise follow the Class II routes (CRA Art. 8(1), 32(2)–(4)).
- After a successful assessment, you draw up the EU declaration of conformity, affix the CE marking, and keep the technical documentation and the declaration for at least 10 years after placing on the market or for the support period, whichever is longer (CRA Art. 13(12)–(13), 28, 30).
Which procedure your product class allows
| Class | Self-assessment (module A) | Notified-body or certification routes | Article |
|---|
| Not in Annex III or IV | Yes | Modules B + C, module H, or a European cybersecurity certification scheme where available and applicable | 32(1) |
| Important, Class I | Only if harmonised standards, common specifications or a certification scheme at assurance level at least "substantial" are applied in full | Otherwise modules B + C or module H | 32(2) |
| Important, Class II | No | Modules B + C, module H, or a certification scheme at assurance level at least "substantial" | 32(3) |
| Critical | No | A certification scheme under a delegated act adopted under Article 8(1); where the Article 8(1) conditions are not met, the Class II routes | 32(4), 8(1) |
| Free and open-source software in an Annex III category | Yes, if the technical documentation is public when the product is placed on the market | Any Article 32(1) route | 32(5) |
You may always choose a stricter procedure than your class requires (CRA Art. 32(1); Guidance, footnote 23). For Class I, the harmonised standards that count are those whose references are published in the Official Journal (Guidance, points 148–149).
What each procedure involves
- Module A, internal control. You draw up the technical documentation (Annex VII), make sure design, development, production and vulnerability handling meet Annex I, affix the CE marking and draw up the EU declaration of conformity, all on your sole responsibility (CRA Annex VIII Part I).
- Module B, EU-type examination. You apply to a single notified body of your choice. It examines the technical design and your vulnerability handling processes, issues an EU-type examination certificate if they meet Annex I, and carries out periodic audits of your vulnerability handling processes (CRA Annex VIII Part II, points 1, 3, 6, 8).
- Module C, conformity to type. You make sure that production matches the approved type, then affix the CE marking and draw up the declaration of conformity for the product model (CRA Annex VIII Part III).
- Module H, full quality assurance. A notified body assesses your quality system for design, development, final inspection, testing and vulnerability handling, including an assessment visit to your premises where they exist, and then audits it periodically. You keep the system effective throughout the support period (CRA Annex VIII Part IV, points 2, 3.3, 4).
- European cybersecurity certification. A certificate or EU statement of conformity under a scheme adopted under Regulation (EU) 2019/881 means the product is presumed to conform to the extent the certificate covers Annex I. Where the Commission specifies such a scheme by delegated act, a certificate at assurance level at least "substantial" removes the need for a third-party assessment under Article 32(2)–(3) for the requirements it covers (CRA Art. 27(8)–(9)).
Member States notify the bodies that carry out these assessments, and the Commission keeps a public list of notified bodies with their identification numbers. These rules have applied since 11 June 2026 (CRA Art. 35(1), 44, 71(2)).
Critical products and the EUCC scheme
The Commission may adopt delegated acts requiring products in specified Annex IV categories to obtain a European cybersecurity certificate at assurance level at least "substantial", but only once a scheme covering those categories has been adopted under Regulation (EU) 2019/881 and is available (CRA Art. 8(1)). The Common Criteria-based scheme (EUCC), adopted by Implementing Regulation (EU) 2024/482, is one such scheme (EUCC). If a delegated act under Article 8(1) names the EUCC for a category, products in that category would need a certificate under it. Until such an act applies, critical products use the Class II routes (CRA Art. 32(4)).
- The EU declaration of conformity states that fulfilment of the Annex I requirements has been demonstrated, follows the model in Annex V (eight items, from product identification to the signature) and is updated as appropriate. By drawing it up, you assume responsibility for the product (CRA Art. 28(1)–(2), (4); Annex V).
- Where several EU acts require a declaration, you draw up a single one (CRA Art. 28(3)). You may ship a simplified declaration (Annex VI) that gives the internet address of the full one (CRA Art. 13(20)).
- The CE marking goes on the product visibly, legibly and indelibly or, where that is not possible, on the packaging and the declaration. For software it goes on the declaration or on the website accompanying the software (CRA Art. 30(1)). It is affixed before the product is placed on the market and, under module H, is followed by the notified body's identification number (CRA Art. 30(3)–(4)).
To check this for your product with an AI assistant, add Shieldbook to Claude or connect the Shieldbook MCP server (https://shieldbook.ppftec.com/mcp); the scope check is also at https://shieldbook.ppftec.com/check.
FAQ
Can I use a notified body even if self-assessment is allowed for my product?
Yes. Article 32(1) lets the manufacturer use any of the procedures it lists, and the Commission notes that a stricter procedure can always be chosen (CRA Art. 32(1); Guidance, footnote 23).
Where does the CE marking go on a software product?
On the EU declaration of conformity or on the website accompanying the software product. If you use the website, the relevant section must be easily and directly accessible to consumers (CRA Art. 30(1)).
Do I repeat the assessment after a substantial modification?
When the original manufacturer substantially modifies a product, the modified product counts as newly placed on the market. In the Commission's reading, you may reuse existing documentation and tests for parts that are not affected and focus the assessment on the substantially modified parts (Guidance, points 122–123).
Sources
Opened by the compliance analyst; dates are when each source was last read.
- Regulation (EU) 2024/2847 (Cyber Resilience Act), OJ L, 20.11.2024. Citation URL: https://eur-lex.europa.eu/eli/reg/2024/2847/oj/eng. File read (authentic OJ PDF via the Publications Office): https://publications.europa.eu/resource/cellar/21b7d4eb-a6e2-11ef-85f0-01aa75ed71a1.0006.01/DOC_1. Art. 8, 13, 27–33, 35, 43, 44 and 71 and Annexes V–VIII read 2026-11-21.
- European Commission, Commission guidance on the application of Regulation (EU) 2024/2847 (Cyber Resilience Act), Communication C/2026/6013, OJ C, 17.11.2026, not binding (point 8). Citation URL: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=OJ:C_202606013. File read: https://publications.europa.eu/resource/cellar/dcbc848b-e227-11f1-aefc-01aa75ed71a1.0006.01/DOC_1. Points 8, 121–140 and 145–155 with footnotes 22–27 read 2026-11-21.
- Commission Implementing Regulation (EU) 2024/482 of 31 January 2024 on the European Common Criteria-based cybersecurity certification scheme (EUCC), OJ L, 7.2.2024. Citation URL: https://eur-lex.europa.eu/eli/reg_impl/2024/482/oj/eng. File read: https://publications.europa.eu/resource/cellar/687c0d05-c580-11ee-95d9-01aa75ed71a1.0006.01/DOC_1. Title page and recitals 1–4 read 2026-11-21.
The Shieldbook kit: templates and worked examples
This site needs JavaScript for the scope checker and the waitlist form.