RBE·11 · RBE Deterministic Suite · DORA Incident Reporting DORA Enforcement Active — Jan 2025

DORA ICT Incident Classification & Reporting Engine

Apply all 7 RTS 2024/1772 materiality criteria with compound classification logic. Compute exact 4-hour / 72-hour / 1-month reporting deadlines. Draft ITS 2025/302 Annex I initial notifications. Flag threshold proximity. Export incident Policy Mandate JSON. Client-side. Zero PII.

DORA Reg (EU) 2022/2554 RTS (EU) 2024/1772 ITS 2025/302 7 Classification Criteria Compound Logic 4h / 72h / 1-month Clock Policy Mandate · Zero PII
⚡ Client-side · No server calls Major incident classification per DORA Art. 18 affects 4-hour reporting deadline compliance. Last Reviewed · 2026-05-12
🔒 Zero PII
📦 MCP-compatible · manifest.json
v RBE Suite v1.0
A — Incident Identity
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Educational Use Only This tool provides a self-assessment / educational framework for internal planning purposes only. It is not a regulatory audit, legal advice, or a substitute for a formal compliance review by a qualified advisor. Verify all interpretations against the official source text and applicable RTS/ITS/guidance published by the relevant authority.
B — Classification Criteria (RTS 2024/1772 — All 7)
C1
Clients / financial counterparties / transactions affected
—
Major: >100,000 clients or >10% · Significant: 100–100,000 or 1–10% · Minor: <100 or <1%
C2
Reputational impact
—
C3
Duration of disruption
—
Major: >24h or ongoing · Significant: 2–24h · Minor: <2h
C4
Geographic spread
—
C5
Data losses (integrity, confidentiality, availability)
⚠ Confirmed breach alone satisfies Condition B1 — Major classification may follow even if only C6 also at Major
—
C6 ★
Criticality of services affected
★ PREREQUISITE — Condition A. Must be Major for Major classification to be possible
—
C7
Economic impact (direct costs + losses, €)
—
Major: >€100,000 · Significant: €25,000–€100,000 · Minor: <€25,000
Classify & Export
Classification Summary
About this tool
All 7 RTS 2024/1772 criteria Implements all seven classification criteria from Commission Delegated Regulation (EU) 2024/1772 (published OJ 25 June 2024, mandatory from 17 January 2025). v2 incorrectly covered 5 — this is the corrected v3 implementation.
Compound Major logic Major requires Condition A (C6 criticality at Major) AND (B1: confirmed data breach OR B2: ≥2 of C1/C2/C3/C4/C7 at Major). A simple threshold breach on any one criterion alone cannot produce a Major classification.
Reporting clock Initial notification: 4h from classification. Intermediate report: 72h from initial notification submission (not classification — corrected per Final RTS July 2024). Final report: 1 month from classification.
ITS template Pre-filled notification draft follows EU Regulation 2025/302 Annex I (published 20 February 2025) — the current legally binding submission form for NCAs.
Regulatory coverage DORA (EU) 2022/2554 Art. 17–20 · RTS (EU) 2024/1772 · ITS EU 2025/302 · NIS2 (EU) 2022/2555 
{
  "tool_id": "rbe-11-dora-incident-classifier",
  "version": "1.0.0",
  "title": "DORA ICT Incident Classifier",
  "category": "ai",
  "ap2_export": true,
  "mandate_type": "incident_classification_mandate",
  "mcp_tool_definition": {
    "name": "classify_dora_ict_incident",
    "description": "Classify ICT incidents under all
7 DORA RTS 2024/1772 criteria. Compute
4h/72h/1-month deadlines. Draft ITS 2025/302
Annex I notification. Proximity warnings.",
    "inputSchema": {
      "type": "object",
      "required": ["classification_time",
        "clients_affected_count",
        "geographic_spread",
        "reputational_data_impact"]
    }
  },
  "execution": {
    "type": "browser-javascript",
    "entry": "tools/rbe-11-dora-incident-classifier.html",
    "function_name": "classifyIncident",
    "timeout_ms": 5000
  }
}