DORA ICT Incident Classification & Reporting Engine · RBE·11

Browser-based DORA ICT incident classification rule engine. Apply all 7 RTS 2024/1772 materiality criteria, compute 4-hour / 72-hour / 1-month reporting deadlines, draft ITS 2025/302-format initial notifications, and export incident Policy Mandate JSON. Zero PII. Client-side. Works offline.

Tool URL: https://ainumbers.co/tools/rbe-11-dora-incident-classifier.html AP2/Policy Mandate export: yes

post/v1/tools/dora_incident_classifier

Request

  • Base URL: https://ainumbers.co
  • URL: https://ainumbers.co/v1/tools/dora_incident_classifier
  • Auth: none declared

Request body

incident_reference_idstring

Internal reference — not PII

detection_timestring date-time
classification_timestring date-time required

4-hour reporting clock starts from this timestamp

ict_service_typestring
entity_typestring

One of 20 DORA Article 2(1) entity types

clients_affected_countinteger
clients_affected_pctnumber
reputational_impact'none' | 'internal' | 'public'
duration_hoursnumber
ongoingboolean

If true, treated as >24h for classification purposes

geographic_spread'single_site' | 'multi_country' | 'cross_border'
data_losses'none' | 'temporary' | 'confirmed_breach'

confirmed_breach alone triggers Condition B1 for Major classification

criticality_of_services'non_critical' | 'important_impacted' | 'critical_adversely' required

Must be critical_adversely (Major) to satisfy Condition A — prerequisite for Major classification

economic_impact_eurnumber
economic_not_quantifiableboolean

Response

Successful tool execution result

reporting_deadlinesobject
initial_notification_draftobject
ap2_mandateobject

Changes

No recorded changes to this operation across all 1 revision of this API.