Skip to contentArticle 14 reporting has applied since 11 September 2026. See the worked example and get the free 4-page overview.
See the kit

Article 14 Reporting Pack

A procedure, notification templates and a case record for the Article 14 deadlines.

Since 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe incidents having an impact on the security of their products through ENISA's Single Reporting Platform (Art. 14, Art. 71(2)). The obligation covers products within the scope of the CRA (Art. 2), including those placed on the market before 11 December 2027 (Art. 69(3)).

  1. Awareness

    The clock starts when you become aware

  2. Within 24 hours

    Early warning, without undue delay

  3. Within 72 hours

    Notification

  4. Final report

    Vulnerability: no later than 14 days after a corrective or mitigating measure is available · Severe incident: within one month after the incident notification

Article 14 of Regulation (EU) 2024/2847. The 24-hour and 72-hour deadlines run from the moment you become aware. Reports go through ENISA's Single Reporting Platform.

Inside the Article 14 pack

See how reporting preparation works.

The playbook brings the reportability decision and team exercises into the same workflow. These are two excerpts from the PDF included in the pack.

Prepare the procedure, then practise it

  1. Assess

    Article 14

    Use the decision tree to assess reportability.

  2. Prepare

    24 h / 72 h

    Draft the relevant notification using the templates.

  3. Record

    Case file

    Keep the facts and decisions in the case file.

  4. Practise

    Playbook

    Test the procedure with a tabletop scenario.

Decision treeArticle 14

Work through the reporting question.

The decision tree separates actively exploited vulnerabilities from severe incidents and shows the reporting steps that follow.

CRA_Article_14_Reporting_Playbook_v1.2.pdf · 8

Selected excerpts from the English-language reporting playbook. Select an image to enlarge it.

In the pack

Reporting playbook

Triggers, deadlines, roles and a decision tree with separate tests for vulnerabilities and incidents; the coordinating CSIRT and what to tell users.

PDFWord

Notification templates

Early warning, notification, intermediate and final reports, and the user advisory, ready to fill in.

Word

Case file and exercise record

A record for every case, and six tabletop scenarios to rehearse before a real one.

Word

Files in the pack (6)

  • 00_README_Article_14_Pack (PDF): where to start
  • CRA_Article_14_Reporting_Playbook (PDF, version 1.2)
  • M06-01 Article 14 Reporting Playbook (Word, version 1.2)
  • M06-02 Article 14 Notification Templates (Word, version 1.1)
  • M06-03 Reporting Case File and Exercise Record (Word, version 1.1)
  • 01_Licence_and_Update_Policy (PDF, version 1.2)

Run your own clock

The legal deadlines run from the moment you become aware. ENISA's FAQ on the Single Reporting Platform (question 26, page updated 17 September 2026) says that in the current release the 72-hour counter shows a due time 48 hours after the early warning was submitted, and that there is no counter for the final report on an actively exploited vulnerability. ENISA also says the counters do not replace the manufacturer's responsibility to meet the deadlines. The playbook shows how to record the moment of awareness and calculate each deadline from it.

Need the full kit? The pack is included in it.