All CRA deadlines at a glance
The Cyber Resilience Act (Regulation (EU) 2024/2847) does not take effect on a single date. The obligations apply in stages: first the rules for conformity assessment bodies, then the reporting obligations, and finally all remaining manufacturer obligations. The timeline contains every date you need to know as a manufacturer, importer or distributor.
The Regulation is published in the Official Journal of the European Union. The text is now final.
Twenty days after publication, the CRA enters into force (Art. 71(1)). No obligations for companies arise yet, but the clock is running.
Art. 35 to 51 apply. Member States can notify conformity assessment bodies for the CRA. This creates the market for CRA assessments that manufacturers of important and critical products need.
Manufacturers must report actively exploited vulnerabilities and severe incidents via the ENISA single reporting platform: early warning within 24 hours, notification within 72 hours. This also applies to products that were already on the market before this date (Art. 69(2)).
All remaining obligations apply (Art. 71(2)): essential requirements under Annex I, risk assessment, conformity assessment, EU declaration of conformity, CE marking, technical documentation, support period.
Products placed on the market before 11 December 2027 fall under the CRA only if they are substantially modified afterwards. The reporting obligation has nevertheless applied to them since 11 September 2026.
The countdown shows the time remaining until full application on 11 December 2027. For the reporting obligations, the deadline has already passed; what the reporting process must look like is explained on the page on CRA reporting obligations.
What must be done by when
Plan backwards from 11 December 2027. From that day, a product with digital elements may only be placed on the market with a declaration of conformity and CE marking. The conformity assessment is the last step and requires complete technical documentation. The documentation in turn requires processes that are actually practised, and those cannot be demonstrated in two weeks. The table shows a realistic plan for a mid-sized product portfolio. Anyone who needs a notified body must start earlier: assessment capacity is scarce, and bodies have only been designated since June 2026.
| Deadline | Work package | Outcome |
|---|---|---|
| Q4 2026 | Gap analysis and product inventory | List of all products with classification (default, important class I or II, critical), gaps against Annex I, prioritisation by revenue and risk. |
| Q1 2027 | Cybersecurity risk assessment per product (Art. 13(2)) | Documented assessment that determines which requirements from Annex I Part I apply and how they are implemented. |
| Q1 2027 | SBOM and component process | Software bill of materials (SBOM) covering at least top-level dependencies, due diligence process for third-party components and open source (Art. 13(5)). |
| Q2 2027 | Vulnerability handling processes (Annex I Part II) | Coordinated vulnerability disclosure policy, point of contact, security testing, update process that separates security updates from functionality updates. The reporting process under Art. 14 must already be running. |
| Q3 2027 | Technical documentation and user information | Technical documentation under Annex VII, user information under Annex II, defined support period of at least five years (Art. 13(8)). |
| Q3 to Q4 2027 | Conformity assessment | Module A internally or module B+C or H with a notified body; EU declaration of conformity under Annex V, CE marking under Art. 30. |
| 11 December 2027 | Placing on the market only in conformity | Every product shipped from this day and every substantially modified existing product complies with the CRA. |
Penalties (Art. 64): Infringements of the essential requirements under Annex I and of Art. 13 and 14 can be fined up to € 15 million or 2.5 % of worldwide annual turnover. For the remaining obligations, fines of up to € 10 million or 2 % apply, and for incorrect information supplied to authorities up to € 5 million or 1 %. German market surveillance is currently being regulated in a national implementing act; the responsibility of the Federal Network Agency (BNetzA) and the BSI is planned but not yet decided.
Transition rule for existing products
For many manufacturers, Art. 69 is the most important provision for scheduling, and it is often misread. The decisive concept is placing on the market: the first making available of an individual product on the Union market. The rule therefore refers to the specific unit, not to the product series or model.
- Shipped before 11 December 2027: The unit remains outside the CRA as long as it is not substantially modified (Art. 69(1)). The reporting obligation under Art. 14 has nevertheless applied since 11 September 2026 (Art. 69(2)).
- Shipped from 11 December 2027: The unit must comply with the CRA, even if the model has been on the market unchanged for years.
- Substantial modification: A change after placing on the market that affects conformity or changes the intended purpose (definition in Art. 3). A major firmware release with new functions may qualify; a pure security update usually does not. Anyone who substantially modifies a third-party product becomes a manufacturer themselves (Art. 22).
Plan per model, therefore, whether you will make it conformant by the deadline or discontinue it beforehand.
Harmonised standards: status as of 26 October 2026
Harmonised standards are the most convenient route to conformity: anyone who applies them in full benefits from the presumption of conformity (Art. 27) and may self-assess class I products. The European Commission has issued standardisation request M/606 to CEN and CENELEC; the technical committee CEN-CLC/JTC 13 develops the horizontal standards, while ETSI and CEN/TC 224 deliver vertical product standards. The delivery dates have been postponed several times. As of 26 October 2026, not a single CRA standard has been cited in the Official Journal, so there is no presumption of conformity yet.
| Standard | Content | Status (as of 26 October 2026) |
|---|---|---|
| EN 40000-1-1 | Vocabulary of the standards series | Formal vote completed, ratification announced for early November 2026. No citation in the Official Journal planned. |
| EN 40000-1-2 | Principles of cyber resilience, product risk management, lifecycle activities | Formal vote completed, ratification announced for early November 2026. No citation in the Official Journal planned. |
| prEN 40000-1-3 | Vulnerability handling (Annex I Part II) | Draft, public enquiry completed, in the approval procedure. Citation in the Official Journal expected, date open. |
| prEN 40000-1-4 | Generic security requirements (Annex I Part I) | Under development. Delivery target under the standardisation request October 2027 (expected). |
| ETSI EN 304 617 to 304 636 | Vertical standards for class I and class II products: browsers, password managers, anti-malware, VPN, network management, SIEM, boot managers, PKI, network interfaces, operating systems, routers and switches, smart home, toys, wearables, hypervisors, firewalls | Final drafts since August 2026, approval procedures running until about November 2026 (expected). |
| prEN 50770-1 to -6 | OT profiles: firewalls, network management, network interfaces, VPN, routers and switches, SIEM in industrial environments | Under development (expected 2027). |
| prEN 40001-3, 40002-3, 40003-3, 40004-3 | Microprocessors and microcontrollers with security functions, tamper-resistant microprocessors and microcontrollers, smartcards and secure elements, ASICs and FPGAs | Enquiry completed or ongoing (expected 2027). |
| prEN 40000-10, prEN 40000-11 | Identity management and access control; hardware devices with security boxes | Enquiry completed, approval procedure (expected 2027). |
Designations and dates are taken from the CEN-CENELEC and ETSI work programmes and from public status overviews of October 2026. They are not officially confirmed and may change. The only thing that counts is citation in the Official Journal of the EU. We maintain a continuously updated overview at Status of harmonised CRA standards.
What does this mean for planning? Do not wait for the standards. The requirements have been fixed since 2024; the standards only specify how conformity is demonstrated. Anyone who develops to IEC 62443-4-1 and 4-2 today and uses BSI TR-03183 as a practical guide will keep the gap to the later EN 40000 series small. For class I products, there is one further consequence: without a cited standard, the route runs through a notified body for the time being.
The reporting obligation already applies
Since 11 September 2026, manufacturers have had to report actively exploited vulnerabilities and severe incidents via ENISA's single reporting platform. Anyone who has not yet organised this is already in breach of Art. 14 today, and for all products on the market, not only new ones. The deadlines, the content of each notification and an internal process in five steps are set out on the page on CRA reporting obligations. How this obligation differs from reporting under NIS-2 is shown in the comparison of CRA and NIS-2.
Next steps
First use the CRA applicability check to establish which of your products fall under the Regulation and which class they belong to. This tells you whether you need to plan for a notified body and how much lead time you really have. In our CRA consulting, we prepare a gap analysis with you and an implementation plan that is aligned with your release cycles, not with an abstract deadline.

