EU Cyber Resilience Act: Key Dates for App Teams

Resumo

Pixel’s announcement outlines key Cyber Resilience Act dates for app teams, including Article 14 reporting duties that began on 11 September 2026 and full application on 11 December 2027. It explains how the rules affect apps already on the market, substantial modifications, and upcoming compliance work.

DEV Community

CRA key dates for app teams, 2024–2027

Two dates matter for app teams: 11 September 2026 (reporting, already running) and 11 December 2027 (everything else). The Cyber Resilience Act (CRA) entered into force on 10 December 2024 and applies in full from 11 December 2027 (Article 71). Article 14, the duty to report actively exploited vulnerabilities and severe incidents, has applied since 11 September 2026, and it covers apps that are already on the market (Article 69(3)). An app placed on the market before 11 December 2027 is otherwise in scope only if it is substantially modified from that date (Article 69(2)). As of 16 November 2026, about thirteen months remain before the main obligations apply. The timeline at a glance Date What happened or applies Why an app team cares 23 October 2024 Parliament and Council adopt Regulation (EU) 2024/2847. The text is fixed. 20 November 2024 Published in the Official Journal. Starts the clock for entry into force. 10 December 2024 Entry into force, on the twentieth day after publication (Article 71(1)). No obligations for manufacturers yet. 11 June 2026 Chapter IV, Articles 35 to 51, applies. It covers the notification of conformity assessment bodies. Mostly relevant if your app is an important or critical product and needs a third party. 27 July 2026 The Commission publishes non-binding guidance, C(2026) 5252. The best available reading of scope, support periods and substantial modification. 11 September 2026 Article 14 applies: reporting of actively exploited vulnerabilities and severe incidents. ENISA's Single Reporting Platform launches the same day. You must be able to report today, also for old apps. 11 December 2027 The Regulation applies in full (Article 71(2)). Annex I requirements, vulnerability handling, technical documentation, EU declaration of conformity and CE marking apply to apps placed on the market from this date. 11 June 2028 Certificates issued under other EU cybersecurity harmonisation legislation stay valid until this date, unless they expire earlier (Article 69(1)). Rarely relevant for apps. 2024: adoption and entry into force The CRA, Regulation (EU) 2024/2847, is dated 23 October 2024 and was published in the Official Journal on 20 November 2024. Under Article 71(1) it entered into force on the twentieth day after publication, which is 10 December 2024. Entry into force did not create duties for manufacturers. It started the transition period that ends with Article 71(2). 11 June 2026: notified bodies Article 71(2) brings Chapter IV (Articles 35 to 51) forward to 11 June 2026. This chapter sets up how Member States designate and notify the conformity assessment bodies that will be needed for certain products. Most apps can be assessed by the manufacturer itself, so this date rarely changes your work. It matters if your app turns out to be an important product, such as a password manager or a VPN, because that can bring a third-party assessment into play. See the scope guide for how Annex III products are treated. 27 July 2026: the Commission guidance On 27 July 2026 the Commission published its guidance on the application of the CRA as C(2026) 5252. The Commission describes it as non-binding. It covers scope, including remote data processing solutions and free and open-source software, what counts as a substantial modification, how support periods should be understood, and how to meet the reporting obligations. It is not a legal deadline, but it is the document most useful when you decide whether a specific app is covered. 11 September 2026: reporting started Article 71(2) says Article 14 applies from 11 September 2026. ENISA launched the CRA Single Reporting Platform the same day. Under Article 14, for an actively exploited vulnerability the manufacturer sends: an early warning "without undue delay and in any event within 24 hours" of becoming aware of it; a vulnerability notification within 72 hours of becoming aware; a final report no later than 14 days after a corrective or mitigating measure i...
EU Cyber Resilience Act: Key Dates for App Teams
Powered by Readybot.io

As últimas novidades de Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …