Artifact GuideEU

EU Cyber Resilience Act deadlines and compliance calendar

A cited calendar for the CRA dates that change legal obligations, reporting readiness, and product release planning.

Use it to separate the entry-into-force date, staged application dates, Article 14 reporting clocks, and transitional treatment of existing products.

Author
Sorena AI
Published
Mar 4, 2026
Updated
Oct 15, 2026
Overview

The Cyber Resilience Act has staged application dates. It entered into force in 2024, starts Article 14 reporting in 2026, applies generally in 2027, and contains specific transitional provisions for products already . This calendar separates those dates so teams do not treat a notified-body infrastructure date as the full manufacturer deadline or miss the earlier reporting start.

Section 2

11 June 2026 is a notified-body infrastructure date

Chapter IV is titled notification of conformity assessment bodies. Its provisions are directed mainly at Member States, notifying authorities, and notified bodies, for example the duty for Member States to notify the Commission and other Member States and to designate a notifying authority.

For a manufacturer, 11 June 2026 is still commercially important if a product may need third-party assessment, but it is not the general date when CRA product obligations begin to apply.

  • Map products that may be important or critical products with digital elements and may need a notified body.
  • Track which notified bodies become available for the relevant product category and conformity route.
  • Do not describe 11 June 2026 as the full manufacturer compliance deadline for ordinary products.
Section 3

11 September 2026 starts Article 14 reporting

Article 14 is the earlier operational date for manufacturers. From 11 September 2026, manufacturers must notify actively exploited vulnerabilities and severe incidents having an impact on the security of products with digital elements through the single reporting platform.

The reporting clock for an or severe incident starts when the manufacturer becomes aware of it after Article 14 starts to apply. The Commission FAQ, updated 2 July 2026, says earlier awareness does not create a retroactive notification duty merely because 11 September 2026 arrives. The CRA sets separate stages for early warnings, follow-up notifications, final reports, and user information.

  • : early warning without undue delay and within 24 hours of awareness.
  • : vulnerability notification without undue delay and within 72 hours of awareness, unless the information was already provided.
  • : final report no later than 14 days after a corrective or mitigating measure is available.
  • Severe incident affecting product security: early warning within 24 hours of awareness, incident notification within 72 hours of awareness, and final report within one month after the incident notification.
  • User notice: after becoming aware, inform impacted users and, where appropriate, all users, of the vulnerability or incident and necessary mitigation or corrective measures.
Section 4

Transition rules for products already on the market

Article 69 prevents the transition period from being read too broadly. Products with digital elements before 11 December 2027 are subject to CRA requirements only if, from that date, they undergo a .

That transitional rule does not remove the earlier reporting duty. Article 69 expressly says Article 14 applies to all in-scope products with digital elements that were before 11 December 2027. Placement on the market is assessed for each individual product, so earlier sales of the same model do not exempt units first placed on the market on or after 11 December 2027.

  • Keep a list of in-scope products before 11 December 2027.
  • Flag which releases, repairs, upgrades, or redesigns could become a from 11 December 2027.
  • Assign Article 14 reporting ownership for legacy products before 11 September 2026.
  • Do not assume a pre-2027 market-placement date exempts the product from vulnerability or incident reporting.
Section 5

11 December 2027 is the main application date

From 11 December 2027, the CRA applies generally. Products with digital elements placed on the EU market from that date need the applicable essential cybersecurity requirements, conformity assessment, technical documentation, EU declaration of conformity, CE marking, and economic-operator controls.

The product calendar should therefore work backward from the market-placement date. There is no extra post-application grace period for an individual product first on or after 11 December 2027. Evidence needed for conformity should be produced during design, development, testing, vulnerability handling, release, and support rather than assembled after launch.

  • Classify each product with digital elements and decide the conformity assessment route before release approval.
  • Complete the cybersecurity risk assessment and Annex I mapping before placing the product on the market.
  • Draw up and maintain technical documentation before market placement and update it where appropriate during the support period.
  • Prepare the EU declaration of conformity and CE marking evidence for the product model.
  • Publish user information, including the type of technical security support and the end date of the support period.
Section 6

Retention, certificates, and review dates

The CRA calendar continues after market placement. The regulation ties documentation retention to at least 10 years after placing the product on the market or the support period, whichever is longer, and it includes later review dates for certificates, the reporting platform, and the regulation itself.

These dates are not all manufacturer launch deadlines, but they matter for audit calendars, certification reliance, and regulatory monitoring.

  • Until 11 June 2028: EU type-examination certificates and approval decisions issued for cybersecurity requirements under other Union harmonisation legislation remain valid unless they expire earlier or the other legislation says otherwise.
  • By 11 September 2028: the Commission must report on the effectiveness of the single reporting platform and delayed-dissemination grounds.
  • By 11 December 2030 and every four years afterward: the Commission must submit an evaluation and review report on the regulation.
  • For each product: keep the EU declaration of conformity and technical documentation available for at least 10 years after market placement or for the support period, whichever is longer.
Recommended next step

Turn the CRA calendar into owned readiness work

Use the calendar to assign reporting readiness before 11 September 2026, conformity evidence before 11 December 2027, and retention or review tasks after market placement.

Primary sources

References and citations

ec.europa.eu
Referenced sections
  • Explains that the Article 14 duty applies to awareness after the reporting requirements enter into application rather than retroactively to earlier awareness.
digital-strategy.ec.europa.eu
Referenced sections
  • Confirms the public-facing Commission summary of CRA entry into force, main application, reporting application, CE marking, and manufacturer lifecycle obligations.
"The CRA entered into force on 10 December 2024."
data.europa.eu
Referenced sections
  • Sets the Article 14 application date, reportable events, awareness-based 24-hour and 72-hour stages, final-report deadlines, user-information duty, and single reporting platform route.
eur-lex.europa.eu
Referenced sections
  • Supports Article 69 transitional provisions, Article 70 review dates, Article 71 staged application dates, Article 14 reporting clocks, and documentation retention periods.
"This Regulation shall apply from 11 December 2027."
Show all related guides (55)

CRA Requirements | Annex I, Manufacturer Duties and CE Evidence

Map Cyber Resilience Act requirements from Annex I to manufacturer duties, vulnerability handling, user information, technical documentation, declaration of conformity, and CE marking evidence.

CRA SBOM and Vulnerability Management Template

Build a CRA-ready SBOM and vulnerability handling record with component inventory, triage, remediation, disclosure, reporting, update, and technical documentation fields.

CRA vs RED Cybersecurity Delegated Act

Compare the EU Cyber Resilience Act with the RED cybersecurity delegated act for connected and radio equipment, including scope, timing, evidence, and transition treatment.

CRA Vulnerability Handling and Disclosure | Article 14 Reporting and Security Updates

How EU Cyber Resilience Act manufacturers should run vulnerability intake, remediation, coordinated disclosure, Article 14 reporting, secure updates, and evidence records.

EU CRA Compliance Program for Manufacturers and Economic Operators

Build a Cyber Resilience Act compliance program around product scope, Annex I security requirements, conformity assessment, technical documentation, vulnerability reporting, and market surveillance.

EU CRA vs UK PSTI Product Security Regime

Compare EU Cyber Resilience Act and UK PSTI product-security scope, duties, evidence, dates, actors, and enforcement for connected products.

EU Cyber Resilience Act Checklist for Product Security and CE Marking

A CRA checklist for products with digital elements: scope, Annex I security controls, vulnerability handling, Article 14 reporting, technical documentation, conformity assessment, CE marking, and support-period evidence.

EU Cyber Resilience Act FAQ

Direct CRA FAQ answers on scope, economic-operator roles, essential requirements, vulnerability reporting, conformity assessment, CE marking, support periods, and market surveillance.

EU Cyber Resilience Act Technical Documentation and Audit File

Build a CRA technical file around Article 31 and Annex VII: product scope, risk assessment, vulnerability handling, conformity evidence, testing, updates, and retention.

CRA Blue Guide Concepts FAQ | Placing on the Market, Making Available, Distance Sales

CRA FAQ explaining Blue Guide market-access concepts for products with digital elements: placing on the market, making available, imports, CE marking, operator roles, online sales, stock, and testing exceptions.

CRA CE Marking FAQ | Conformity Assessment, EU Declaration, Evidence

Practical CRA CE marking answers for products with digital elements: conformity assessment, EU declaration, technical documentation, standards, software placement, and launch evidence.

CRA Component Due Diligence FAQ | Third-Party Software, FOSS, SBOMs

Cyber Resilience Act FAQ on manufacturer due diligence for integrated components, third-party software, FOSS dependencies, SBOMs, vulnerability handling, and evidence records.

CRA Conformity Assessment Routes FAQ | Module A, Module B+C, Module H, Important and Critical Products

Cyber Resilience Act FAQ on when manufacturers can use module A, when module B+C or module H is required, and how important and critical products affect the route.

CRA Cybersecurity Risk Assessment FAQ | Article 13, Annex I, Updates

CRA FAQ on Article 13 cybersecurity risk assessments, Annex I applicability, intended purpose, foreseeable use, technical documentation, and update evidence.

CRA Declaration of Conformity FAQ | Annex V, Simplified Declaration, CE Marking

FAQ on the Cyber Resilience Act EU Declaration of Conformity: Annex V contents, simplified Annex VI wording, CE marking link, technical documentation, retention, updates, and operator duties.

CRA Economic Operators FAQ | Manufacturers, Importers, Distributors, Authorised Representatives

CRA FAQ on economic-operator roles: manufacturers, importers, distributors, authorised representatives, substantial modification, traceability, and evidence controls.

CRA Essential Cybersecurity Requirements FAQ | Annex I Part I and Part II

CRA FAQ on Annex I product cybersecurity requirements, vulnerability handling, secure-by-default design, risk assessment, documentation, lifecycle duties, and user information.

CRA Hardware and Software Boundaries FAQ | Product Scope, Components, RDPS

FAQ on Cyber Resilience Act hardware and software boundaries: combined products, standalone software, source code, components, remote data processing, SaaS and market-placement changes.

CRA Harmonised Standards FAQ | Presumption of Conformity, Common Specifications

Cyber Resilience Act FAQ on how harmonised standards, common specifications, certification schemes, and OJ publication affect CRA conformity evidence.

CRA Important and Critical Products FAQ | Annex III, Annex IV, Conformity Assessment

FAQ on CRA important and critical products, Annex III and Annex IV classification, core functionality, and conformity assessment consequences.

CRA Integrated Components and Dependencies FAQ | Third-Party Software and SBOM Evidence

Cyber Resilience Act FAQ on integrated components, third-party software, remote data processing, SBOM-style evidence, upstream fixes, FOSS dependencies, and manufacturer responsibility.

CRA Interplay With EU Product Laws FAQ | RED, Machinery, Data Act

Official source CRA FAQ on overlap with the Radio Equipment Directive, Machinery Regulation, GPSR, Data Act, exclusions, declarations, documentation, and existing certificates.

CRA Known Exploitable Vulnerabilities at Launch FAQ

FAQ for Cyber Resilience Act launch decisions: known exploitable vulnerabilities, CVEs, component flaws, secure-by-default settings, release gates, Article 14 reporting, and evidence.

CRA Legacy Products FAQ | Pre-11 December 2027 Products

Cyber Resilience Act FAQ on products placed on the market before 11 December 2027, Article 14 reporting, substantial modification, distributor stock, spare parts, and records.

CRA Manufacturer Obligations FAQ | Article 13, Annex I, CE Marking

FAQ for Cyber Resilience Act manufacturers covering Article 13 duties, risk assessment, Annex I, vulnerability handling, support periods, documentation, conformity assessment, reporting, CE marking, and evidence controls.

CRA Market Surveillance and Enforcement FAQ | Authorities, Corrective Action, Safeguards

Cyber Resilience Act FAQ on market-surveillance authorities, investigations, corrective action, withdrawal, recall, safeguards, sweeps, documentation access, and penalties.

CRA Module B+C FAQ | EU-Type Examination, Conformity to Type, Notified Bodies

CRA Module B+C FAQ explaining EU-type examination, conformity to type, notified-body evidence, production control, CE marking, declarations, and certificate changes.

CRA Module H FAQ | Full Quality Assurance, Notified Body Surveillance, CE Marking

CRA Module H FAQ explaining the full-quality-assurance route, notified-body assessment, quality-system scope, technical documentation, CE marking, declarations, and records.

CRA Notified Bodies FAQ | Scope, Modules B+C and H, Certificates

Practical CRA FAQ on when notified bodies are needed, how CRA bodies are designated, what their notified scope means, and how Module B+C and Module H assessments work.

CRA Open-Source Software FAQ | FOSS Scope, Stewards, Manufacturers

Cyber Resilience Act FAQ for free and open-source software: commercial activity, steward duties, manufacturer due diligence, vulnerability handling, public documentation, and user obligations.

CRA Over-the-Air Updates FAQ

Cyber Resilience Act FAQ on OTA updates, automatic security updates, secure update distribution, support-period evidence, and offline update paths.

CRA penalties and fines FAQ | Article 64 fine caps

FAQ on EU Cyber Resilience Act Article 64 penalties: maximum fine tiers, turnover caps, national enforcement, economic operators, reporting duties, and open-source steward carve-outs.

CRA Product Families FAQ | Variants, Shared Assessments, Family Reuse, Conformity Scope

CRA FAQ on product families, variant grouping, shared technical documentation, conformity evidence, and when cybersecurity-relevant differences need separate assessment.

CRA Products With Digital Elements Scope FAQ

EU Cyber Resilience Act FAQ on products with digital elements, software, firmware, remote data processing, components, exclusions, market placement, and CRA operator boundaries.

CRA Remote Data Processing Solutions FAQ | Product Scope, Cloud and Backend Boundaries

FAQ on how the EU Cyber Resilience Act treats remote data processing solutions, manufacturer-controlled backends, third-party cloud services, SaaS, risk assessment, documentation, and user information.

CRA Reporting Obligations FAQ | Article 14, CSIRTs, ENISA, User Notices

Cyber Resilience Act FAQ on Article 14 reporting for actively exploited vulnerabilities and severe incidents, including timing, CSIRT routing, ENISA access, user notices, and evidence.

CRA Secure-by-Default FAQ | Default Configuration and Annex I Controls

Cyber Resilience Act FAQ on secure-by-default configuration, automatic security updates, attack surface reduction, authentication, data minimisation, user information, and tailor-made products.

CRA Security Updates vs Functionality Updates FAQ

Cyber Resilience Act FAQ on classifying security updates, functionality updates, support-period duties, automatic updates, user notices, and substantial-modification review.

CRA Substantial Modification FAQ | Updates, Repairs, Manufacturer Duties

Cyber Resilience Act FAQ on when software updates, repairs, spare parts, and post-market changes become substantial modifications and trigger CRA manufacturer, evidence, and conformity duties.

CRA Support Period FAQ | Expected Product Lifetime, Security Updates, User Information

Practical CRA FAQ on how manufacturers determine support periods, disclose support end dates, keep security updates available, and document support-period evidence.

CRA Tailor-Made Products FAQ | Bespoke Products, Market Placement, Evidence

FAQ on when a bespoke product may be treated as tailor-made under the EU Cyber Resilience Act, what the carve-out changes, and what manufacturers still need to document.

CRA Technical Documentation FAQ | Annex VII Evidence and Technical File

CRA FAQ explaining Annex VII technical documentation, risk assessment evidence, conformity assessment files, vulnerability handling records, product families, RDPS, language, and authority access.

CRA Transition Period FAQ | Entry Into Force, Application Dates, Reporting, Legacy Products

CRA FAQ on the transition period covering entry into force, 2026 reporting, 2027 application, legacy products, stock, customs timing, and software versions.

CRA Update Availability and Software Archives FAQ

FAQ on CRA security-update availability, support-period notices, optional public software archives, historical versions, and Article 13(10) software-version limits.

CRA User Information and Transparency FAQ | Annex II Instructions

Practical CRA FAQ on Annex II user instructions, support-period disclosure, vulnerability contacts, update notices, importer and distributor information.

CRA Vulnerability Handling FAQ | Support Periods, Components, Reporting

Practical CRA FAQ on vulnerability handling: SBOMs, remediation, coordinated disclosure, component issues, security updates, support periods, Article 14 reporting, and user notices.

Cyber Resilience Act Module A FAQ | Internal Production Control

FAQ on when CRA Module A internal production control is available, when it is blocked, and what documentation, testing, standards, and evidence it still requires.

EU Cyber Resilience Act Core Functionality FAQ | CRA Product Classification

CRA FAQ on core functionality, product boundaries, remote data processing, integrated components, ancillary functions, and software changes that affect product classification.

EU Cyber Resilience Act Repairs and Spare Parts FAQ

CRA FAQ for repairs, spare parts, legacy products, security updates, substantial modification, and responsibility after product changes.