Repository navigation
Add DORA/NIS2 incident reporting phone-call alerts post (6 languages) - #31
Merged
Merged
Conversation
Covers the regulatory reporting clocks (DORA 4h from classification, NIS2 24h early warning, SEC 4 business days) and how to put a ringing phone call in front of the reporting workflow with Echobell. Anchored on the ESAs' first EU-wide DORA major-incident report (3 June 2026): 3,383 major incidents in 2025, ~1/3 cross-border, only 10% cybersecurity-related. All facts cited to primary sources (EBA, ESMA, European Commission, SEC) with an explicit limitations section on what Echobell does not do. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CVEZzHJsgP9a32sfdd95PB
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
New blog post in all six locales:
content/blog/dora-nis2-incident-reporting-alerts.{mdx,zh,ja,es,fr,de}.mdx.The marketing angle is regulatory incident-reporting clocks — a segment none of the existing 28 slugs covers, and one that maps directly onto Echobell's webhook/email → phone-call positioning: every deadline starts on machine detection and keeps running overnight, so the binding constraint is human acknowledgement, not detection.
News hook: on 3 June 2026 the ESAs published the first EU-wide overview of major ICT-related incidents reported under DORA — 3,383 in 2025, ~1/3 cross-border, and only 10% cybersecurity-related (system failures and external events dominate). That last figure is the argument: the events that start a regulatory clock are the ordinary outages monitoring already catches at 3 a.m.
Content
Citations
All figures verified against primary sources and linked inline:
One caveat: EUR-Lex serves HTTP 202 with an empty body to non-browser clients, so Article 5 of Delegated Regulation (EU) 2025/301 could not be fetched from the official host. Its text was cross-checked against two independent reproductions that agree verbatim, and the EUR-Lex links remain in the post for readers.
Conventions
/en/...internal links; other locales use locale-less linksct=blog-dora-nis2-incident-reporting-alerts-{lang}date: 2026-07-31, author Nooc, avatar, authorLink, tagsValidation
pnpm install --frozen-lockfile— cleanpnpm run build— succeeded; all six language pages prerender ({en,zh,ja,es,fr,de}/blog/dora-nis2-incident-reporting-alerts.html)pnpm run lint— passes, no errors