Annex I is divided into two parts. Part I sets out 13 properties that the product with digital elements must have — from secure-by-default configuration to data minimisation to attack surface reduction. Part II sets out 8 vulnerability handling obligations that the manufacturer must follow throughout the support period — from maintaining a software bill of materials to providing free security updates without delay. Article 6 of Regulation (EU) 2024/2847 states that products may only be placed on the EU market if they meet every applicable requirement in both parts. CRACheck structures the technical documentation required under Article 31 and Annex VII around these 21 requirements. 8 PDFs. 15–25 minutes. €149 per product.
€149 one-time · 8-document ZIP · 15–25 minutes · Browser-side
The 21 requirements of Annex I are not standalone checkboxes. They feed into the cybersecurity risk assessment under Article 13(2), the technical documentation under Article 31, and the user information under Annex II. CRACheck structures this chain in 7 steps.
Annex I Part I point (2) states that requirements apply "on the basis of the cybersecurity risk assessment referred to in Article 13(2) and where applicable." Each requirement must be assessed against the product's specific risk profile. A blanket "compliant" without a documented risk assessment is insufficient under Article 31.
Part II of Annex I is not optional. It requires the manufacturer to maintain an SBOM, operate a CVD policy, distribute security updates free of charge, and provide a contact point for vulnerability reporting. These obligations persist throughout the support period defined under Article 13(8).
Article 64(2) of Regulation (EU) 2024/2847 sets administrative fines of up to €15,000,000 or 2.5% of total worldwide annual turnover for non-compliance with Annex I requirements. This is the highest penalty tier in the CRA.
8 PDF documents generated from your data. Each cites the specific article of Regulation (EU) 2024/2847 it complies with.
Determines your product category (Default / Important Class I / Class II / Critical) by cross-referencing Annex III and Annex IV. The classification determines which conformity assessment procedure under Article 32 applies.
The Annex VII file. Contains the 8 elements required under Article 31: product description, design and development information with system architecture, vulnerability handling processes including SBOM and CVD policy, cybersecurity risk assessment, support period rationale, standards applied, test reports, and EU Declaration of Conformity.
Cybersecurity risk assessment per Article 13(2)–(3), structured against every applicable Annex I Part I requirement. Documents which requirements apply, how they are implemented, and the residual risk for each.
The 9 data points required by Annex II: manufacturer identification, vulnerability contact, product identification, intended purpose with security environment, foreseeable cybersecurity risks, DoC link, support period and type, detailed security instructions, and SBOM availability.
EU Declaration of Conformity per Article 28 and Annex V. Contains: product identification, manufacturer data, conformity statement, harmonised standards or specifications applied, notified body information if applicable, and signature block.
Coordinated vulnerability disclosure policy as required by Annex I Part II point (5). Includes contact point for reporting, expected response timeline, and disclosure coordination process.
Pre-structured template for ENISA and CSIRT notifications under Article 14. Covers the three-stage notification: 24-hour early warning, 72-hour vulnerability notification, and 14-day final report. Art. 14(2): early warning within 24h, notification within 72h, final report within 14 days.
Timeline of CRA obligations with key dates: 11 September 2026 (Article 14 reporting), 11 December 2027 (full enforcement), and product-specific support period milestones.
See before you buy — Download sample dossier (PDF, fictional company) — Real structure, real articles, real format. Fictional data.
Generated from your data, in your browser. No data leaves your device.