EU Cyber Resilience Act: the dates, and which already apply

Article 71 of Regulation (EU) 2024/2847 sets when the Regulation entered into force and when it starts to apply. Two of its dates are already behind us, which is easy to miss because most summaries still write them in the future tense.

Entry into force
Article 71(1): the Regulation “shall enter into force on the twentieth day following that of its publication in the Official Journal of the European Union”. Publication was OJ L 2847 of 20 November 2024, which places entry into force in December 2024. Note that this date is derived from the publication date and that rule — the text does not state it. Already in force
11 June 2026
Article 71(2): “Chapter IV (Articles 35 to 51) shall apply from 11 June 2026.” Chapter IV is headed Notification of conformity assessment bodies — it is the machinery by which Member States designate, notify and supervise the bodies that can perform conformity assessment. It is not an obligation that lands on a manufacturer on that date. Has applied since 11 June 2026
11 September 2026
Article 71(2): “Article 14 shall apply from 11 September 2026”. Article 14 is headed Reporting obligations of manufacturers: notification of an actively exploited vulnerability, and of a severe incident having an impact on the security of the product, to the CSIRT designated as coordinator and to ENISA, via the single reporting platform established under Article 16. The Article sets an early-warning notification within 24 hours and a fuller notification within 72 hours for each, and then two different final-report clocks. For an actively exploited vulnerability, Article 14(2)(c) requires “a final report, no later than 14 days after a corrective or mitigating measure is available”. For a severe incident, Article 14(4)(c) requires “a final report, within one month after the submission of the incident notification under point (b)”. Has applied since 11 September 2026
11 December 2027
Article 71(2): “This Regulation shall apply from 11 December 2027.” This is the general application date — the point at which the remaining obligations take effect for products placed on the market, including the Annex VII technical documentation obligation under Article 31 and the Annex V declaration of conformity obligation under Article 28. Applies from 11 December 2027

Article 71(2) in full

“This Regulation shall apply from 11 December 2027. However, Article 14 shall apply from 11 September 2026 and Chapter IV (Articles 35 to 51) shall apply from 11 June 2026.”

Regulation (EU) 2024/2847, consolidated text 02024R2847-20241120, Article 71(2). Read it on EUR-Lex.

What “already applies” means for Article 14

Article 14 is a live reporting duty, not a documentation duty. It runs on clocks measured in hours, it is owed to a CSIRT and to ENISA through the Article 16 single reporting platform, and it has applied since 11 September 2026.

ceproof does not file or monitor these notifications; it drafts technical documentation. It is an offline document generator with no network calls of any kind. Article 14 is listed on this page because it is part of why you are reading about the CRA at all — not because this tool addresses it. If you need an incident-reporting process, that is a separate piece of work, and it is already overdue.

What the December 2027 date actually covers

The Annex VII technical documentation and the Annex V declaration of conformity both hang off the general application date. Article 31(2) adds that the technical documentation “shall be drawn up before the product with digital elements is placed on the market and shall be continuously updated, where appropriate, at least during the support period” — so it is a document you keep current, not one you file once.

The 21 items that document contains →

Draft yours from your own repository

ceproof lays out all 21 items in the regulation's order, cites each one, derives what your repository can evidence, and lists what is still open. Free to scan and to see the gap checklist. $99, one-time to export the Annex VII pack and the Annex V DoC draft.

Needs a repository with an npm or Python manifest. C or C++ firmware is not supported today.