CRA December 2027 readiness — scope, assessment and evidence checks
What to have in place before CRA product obligations apply on 11 December 2027: scope, class, risk assessment, support period, assessment route, documentation, declaration.
By CenitiaUpdated
Fact-checked against the law as of Reviewed by Vladimír Vician on How we check
From 11 December 2027 every product with digital elements placed on the EU market must comply with the Cyber Resilience Act (Regulation (EU) 2024/2847, Article 71(2)). The reporting duty in Article 14 is not part of this countdown: it has applied since 11 September 2026 and is covered in the CRA reporting checklist. This page lists what a manufacturer needs for the December 2027 date, in the order in which the steps depend on each other.
Readiness checks, in order
- Scope. Confirm that the product is a product with digital elements whose intended purpose or reasonably foreseeable use includes a data connection, and that no exclusion in Article 2 of the Cyber Resilience Act applies.
- Class. Compare the product's core functionality with Annexes III and IV and the technical descriptions in Implementing Regulation (EU) 2025/2392. See CRA Annex III important products.
- Risk assessment. Document the cybersecurity risk assessment required by Article 13(2) and (3). It must state which requirements of Annex I Part I point 2 apply and how they are implemented. See CRA Annex I.
- Existing models. Decide for each model whether units will still be placed on the market from 11 December 2027. Those units must comply. The Commission guidance on the application of the Cyber Resilience Act (C/2026/6013, paragraphs 33 to 35) says a redesign is not necessarily required where the risk assessment shows that existing measures address the risks.
- Support period and vulnerability handling. Set the support period under Article 13(8) and put the Annex I Part II processes in place: software bill of materials, coordinated vulnerability disclosure policy, contact address, secure update distribution. Article 13(19) requires the end date of the support period, at least month and year, to be clear at the time of purchase.
- Assessment route. Choose the route under Article 32. If it needs a notified body, check that the body is notified for the Cyber Resilience Act; the rules on notification in Chapter IV have applied since 11 June 2026, and notified bodies are listed in the Commission's NANDO database. For a Class I product, check whether a harmonised standard has been cited: see CRA harmonised standards.
- Technical documentation. Draw it up before the product is placed on the market, with at least the content of Annex VII, and keep it up to date during the support period (Article 31).
- Declaration, marking and user information. Draw up the EU declaration of conformity (Article 28, Annex V), affix the CE marking (Article 30) and supply the information and instructions listed in Annex II.
- Certificates under other acts. An EU-type examination certificate issued for cybersecurity requirements under other legislation, such as the Radio Equipment Directive delegated act (EU) 2022/30, can be relied on until 11 June 2028 only for the risks it covers (Article 69(1); guidance paragraphs 248 and 249). The other requirements of the Cyber Resilience Act still apply from 11 December 2027.
The dates in this list are the legal ones. How long each step takes depends on the product and on the assessment body, so get current lead times from the body you intend to use.
Existing products and modifications (CRA Article 69)
Three cases need to be kept apart under the Cyber Resilience Act. Products placed on the market before 11 December 2027 are subject to the product requirements only if they are substantially modified from that date (Article 69(2)). Article 14 reporting applies to all in-scope products, including those placed on the market earlier (Article 69(3)). Every unit placed on the market from 11 December 2027 must comply in full, even if the model is older: the Regulation applies from that date (Article 71(2)) and placing on the market is assessed for each individual unit. Units still in the stock of the manufacturer or importer that have not yet been supplied for distribution or use have not been placed on the market, so Article 69(2) does not cover them.
CRA manufacturer duties, support period and retention (Regulation (EU) 2024/2847, Article 13)
Under the Cyber Resilience Act, for products placed on the market from 11 December 2027, the manufacturer documents a cybersecurity risk assessment and the technical evidence (Article 13(2) to (4), Annex VII). Article 13(8) requires a support period that reflects the time the product is expected to be in use, taking reasonable user expectations into account; it is at least five years unless the expected use is shorter. Article 13(13) requires the technical documentation and the EU declaration of conformity to be kept for at least ten years after the product is placed on the market or for the support period, whichever is longer. Annex VII lists the content of the technical documentation.
CRA conformity assessment (Regulation (EU) 2024/2847, Article 32)
Under the Cyber Resilience Act, Annex VIII sets out internal control (module A), EU-type examination plus conformity to type (modules B+C) and full quality assurance (module H). These routes apply to products placed on the market from 11 December 2027. Products outside Annexes III and IV may use module A. An important product of Class I may use module A only for requirements covered by harmonised standards, common specifications or a European cybersecurity certification scheme at assurance level at least 'substantial' that the manufacturer has applied; where these are not applied, are applied only in part or do not exist, Article 32(2) requires B+C or H. Class II needs B+C, H or, where available and applicable, a European cybersecurity certification scheme at assurance level at least 'substantial' (Article 32(3)). Article 32(5) lets manufacturers of free and open-source software in the Annex III categories use any of the Article 32(1) procedures, including module A, provided the technical documentation is made available to the public when the product is placed on the market. For critical products (Annex IV), Article 32(4) requires a European cybersecurity certification scheme where one is mandated under Article 8(1), and otherwise the Class II routes. From 26 March 2027, Article 32(5a), inserted by Regulation (EU) 2025/327 on the European Health Data Space, requires EHR systems under that Regulation to use its conformity assessment procedure instead. Classify by the product's core functionality against Annexes III and IV and the technical descriptions in Implementing Regulation (EU) 2025/2392, not by a component name.
EU declaration of conformity (Regulation (EU) 2024/2847, Article 28)
Under Article 28 of the Cyber Resilience Act the manufacturer draws up an EU declaration of conformity stating that fulfilment of the applicable Annex I requirements has been demonstrated. It follows the model structure in Annex V, is kept up to date and is made available in the languages required by the Member State where the product is placed or made available on the market. Where the product falls under several Union acts that require a declaration, Article 28(3) requires a single declaration that identifies all of them.
Article 13(20) lets the manufacturer supply either a copy of the full declaration with the product or the simplified declaration in Annex VI, which must give the exact internet address of the full text.
By drawing up the declaration the manufacturer assumes responsibility for the compliance of the product (Article 28(4)). List only the standards and specifications that were actually applied and the conformity assessment that was actually completed.
Primary references
- Regulation (EU) 2024/2847 (Cyber Resilience Act), EUR-Lex
- Commission Implementing Regulation (EU) 2025/2392 (technical descriptions of important and critical product categories), EUR-Lex
- Commission guidance on the application of the Cyber Resilience Act (C/2026/6013), EUR-Lex
- European Commission: Cyber Resilience Act conformity assessment
FAQ
Frequently asked questions
What changes on 11 December 2027 under the Cyber Resilience Act?
From 11 December 2027 the whole of Regulation (EU) 2024/2847 applies (Article 71(2)). Every product with digital elements placed on the EU market from that date must meet the essential cybersecurity requirements in Annex I, have technical documentation under Annex VII, pass the conformity assessment required by Article 32, carry the CE marking and come with an EU declaration of conformity. Article 14 reporting has already applied since 11 September 2026.
Does an existing product model have to be redesigned for the CRA?
Not necessarily. Units placed on the market from 11 December 2027 must comply even if the model was designed earlier. The Commission guidance on the application of the Cyber Resilience Act (C/2026/6013, paragraphs 33 to 35) says the manufacturer must carry out the risk assessment and may rely on existing security measures where they already address the relevant risks; the conformity assessment, declaration and CE marking are required in any case. The guidance is not legally binding.
Do I need a notified body for the CRA?
It depends on the class. Under Article 32 of the Cyber Resilience Act, products outside Annexes III and IV can use internal control (module A). A Class I important product can use module A only where harmonised standards, common specifications or an eligible certification scheme are applied; otherwise it needs modules B+C or H. A Class II product needs B+C, H or an eligible European cybersecurity certification scheme. As an exception, free and open-source important products can use module A if the technical documentation is public.
How long must CRA technical documentation be kept?
Article 13(13) of the Cyber Resilience Act requires the manufacturer to keep the technical documentation and the EU declaration of conformity at the disposal of market surveillance authorities for at least ten years after the product is placed on the market or for the support period, whichever is longer.
Continue reading
Related guides
tutorial
Secure OTA Firmware Updates and the Evidence to Keep
Plan secure OTA test evidence for signatures, interrupted updates, recovery and downgrade controls against the CRA update requirements, with a small host demo.
6 min read
guide
CRA Scope for Connected Devices and Their Cloud Backends
Apply the CRA remote data processing tests to connected device architectures and record external cloud dependencies separately.
5 min read
guide
When a Firmware Update Needs New CE Evidence or Retesting
Assess firmware changes against existing CE evidence, notified body notification duties and the CRA substantial modification rules with a change impact record.
6 min read
tutorial
CycloneDX VEX for Embedded Firmware: a Worked Synthetic Example
Write a scoped CycloneDX VEX decision for embedded firmware: an unresolved in_triage record, a synthetic not_affected record with justification, and reassessment triggers.
5 min read
Put this into practice
Free tools & references
- CRA Readiness CheckerScore your product against the Cyber Resilience Act essential requirements.Open tool →
- EU Directive SelectorDescribe your product and find which EU directives and regulations apply.Open tool →
New to the terminology? Browse the compliance glossary — plain-English, citation-backed definitions of every term above.