Skip to content

Add DORA/NIS2 incident reporting phone-call alerts post (6 languages) - #31

Merged
noobnooc merged 1 commit into
mainfrom
claude/beautiful-franklin-72x740
Aug 2, 2026
Merged

noobnooc merged 1 commit into
mainfrom
claude/beautiful-franklin-72x740

Conversation

@noobnooc

@noobnooc noobnooc commented Jul 31, 2026 •

Copy link
Copy Markdown
Member

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

  • One H1 promise statement; direct answer sentence opening each H2/H3
  • Comparison table of DORA (4h from classification / 24h outer bound / 72h / 1 month), NIS2 Art. 23(4) (24h / 72h / 1 month), and SEC Item 1.05 (4 business days)
  • Section on the DORA weekend/bank-holiday extension and the carve-out that withholds it from credit institutions, CCPs, trading venue operators, and NIS2 essential/important entities
  • Six-step setup: Calling channel → detection stack webhook → conditions filter → email trigger fallback → shared channel for whoever owns the deadline → test with DND on
  • Explicit "what Echobell does not do" section: no classification, no filing, no GRC/audit trail, no compliance attestation, no delivery guarantee
  • 8-question FAQ

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

  • English uses /en/... internal links; other locales use locale-less links
  • Per-language App Store campaign token: ct=blog-dora-nis2-incident-reporting-alerts-{lang}
  • Frontmatter: title, description, date: 2026-07-31, author Nooc, avatar, authorLink, tags

Validation

  • pnpm install --frozen-lockfile — clean
  • pnpm 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
  • Every internal link target verified present in the prerendered output

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
@noobnooc
noobnooc merged commit 06f5243 into main Aug 2, 2026
1 check passed
@noobnooc
noobnooc deleted the claude/beautiful-franklin-72x740 branch August 2, 2026 01:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants