Skip to content

Article 14 deadline calculator

Enter when you became aware of an actively exploited vulnerability or a severe incident. The calculator shows when the early warning, the notification and the final report are due, in UTC and in your time zone, and lists the fields ENISA’s Single Reporting Platform asks for at each stage.

Information only, not legal advice. The calculator counts the deadlines the way the BitHive Reporting Desk counts them, as set out under “How the deadlines are counted”. Whether and how Article 14 applies to your product is a question for your own legal counsel.

The calculation runs entirely in your browser: what you enter is not sent to us, the page sends nothing while you use it, and it sets no cookie. It needs JavaScript (one script from this site); without it, the rules below still explain how each deadline is counted.

How the deadlines are counted

  • The early warning is due 24 hours, and the notification 72 hours, after you became aware of the actively exploited vulnerability or the severe incident (Article 14(2)(a) and (b), 14(4)(a) and (b)). The hours count from the minute you became aware.
  • For a vulnerability, the final report is due 14 days after a corrective or mitigating measure is available (Article 14(2)(c)), counted as 14 × 24 hours from that minute.
  • For a severe incident, the final report is due one month after the notification (Article 14(4)(c)): at the same time of day on the same date a month later, or on the last day of that month when it has no such date, so 31 January gives 28 February, or 29 February in a leap year, and 31 March gives 30 April. The month is counted both in UTC and on Berlin’s clock, and the earlier of the two is the deadline. Where counting on the calendar of your own time zone ends earlier still, the calculator shows that time as well.
  • The deadlines run continuously: weekends and public holidays are not excluded.
  • Times are read on the clock of the time zone you choose. When the clocks go back and a time occurs twice, the earlier one counts, because it starts the deadline sooner. For a time the clocks skip when they go forward, the page shows how it is read.

Sources

Whom to notify in each member state, with the sources

In the Reporting Desk

Upload your SBOM, or send each new one from your pipeline. Every hour, each monitored release is checked for actively exploited vulnerabilities listed by CISA KEV and ENISA EUVD, matched with OSV advisory data to its components from npm, PyPI, Maven, Go, NuGet, RubyGems, crates.io and Debian; when a monitored component is affected, a case opens with its clock already running. In the BitHive Reporting Desk, each deadline runs from the point the law sets – the moment you became aware, the submission of an earlier report or a request from the authority – as recorded in the case. Each report starts as a draft with the details the authority asks for, and the people you name are alerted before every deadline. If nobody has opened or acknowledged the case two hours after its clock started, your named backup is alerted as well. See how the Reporting Desk works

This page / In the Reporting Desk
This pageIn the Reporting Desk
Who is toldYou, here and nowThe people you name, by e-mail, Slack, Microsoft Teams or webhook. If nobody has opened or acknowledged the case two hours after its clock started, your named backup is alerted as well
The reportThe list of what the authority asksA draft with the details the authority asks for, for you to complete and submit, with the submission time recorded
ProofYour entries stay in your browser and are not storedA timestamped record of every step, decision and submission, ready to export
Over timeA single incident, calculated nowEvery case with its deadlines and reminders, until it is closed

General information, not legal advice.

Start free 14-day trial