ART-467 · DORA ICT Incident Classification

DORA ICT Incident Classifier & Reporting Clock

Classifies an ICT-related incident as major or non-major under DORA (EU) 2022/2554 Art. 18, applying the published RTS (EU 2024/1772) numeric criteria across seven severity dimensions, then starts the Art. 19 reporting clock (4-hour initial notification, 72-hour intermediate report, 1-calendar-month final report) once classified major. Emits a hash-anchored OpenChainGraph v0.4 artifact.

Classification clock, not a filing system
Not legal advice
🔒 All inputs are processed locally in your browser. No data is transmitted. Use synthetic or anonymised inputs only, do not enter real personal or confidential data.
Scope limits, read before use: the numeric thresholds pinned here (10% clients affected, 24h duration, 2 member states, EUR 100,000 economic impact) are MODERATE-confidence citations of the 2024 RTS/ITS headline figures, not a certified reproduction of the full regulation text, which combines several per-criterion nuances this tool does not model (e.g. absolute-count limbs, entity-type-specific relative thresholds). Verify against the final consolidated RTS/ITS text at legal review before relying on this verdict for an actual filing. A DORA incident classifier already ships as ART-09 (earlier draft-RTS citation, no reporting-clock link); this tool cites the final 2024 RTS/ITS package and follows the ART-428 notification-clock pattern instead; the overlap between the two is a known open question, not hidden.
When the incident was classified. Reporting clocks start here if MAJOR.
CriterionMetValue
OpenChainGraph v0.4 artifact · execution_hash:

    
    
  


  

    
Related

    
Follows the ART-428 Cyber Incident Notification Clock deadline-clock pattern for the EU DORA regime. Distinct from ART-466 DORA RoI Builder, which validates the standing Register of Information dataset rather than classifying a single incident. See also the existing ART-09 DORA Incident Classifier (earlier draft-RTS citation, standalone, no notification-clock link).

  











  

    
Ask your agent

    
  

  
Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this exact tool, with this sample, and verify the artifact.

  
Run the AINumbers MCP tool `classify_dora_ict_incident_and_clock_deadlines`. Task: Classify an ICT-related incident as major or non-major under DORA (EU 2022/2554) Art.
Call it with arguments: {"policy_parameters":{"incident_id":"INC-2026-0100","classification_at":"2026-07-20T09:00:00Z","clients_affected_pct":2,"duration_minutes":30,"geographical_spread_countries_count":1,"data_losses":false,"economic_impact_amount":5000,"critical_services_affected":false,"reputational_impact":false}}
Verify before trusting: call `verify_execution_hash` on mcp.ainumbers.co (https://mcp.ainumbers.co/mcp) with the parameter `claimed_hash` set to the returned `execution_hash`, or re-run the in-page WebMCP tool `classify_dora_ict_incident_and_clock_deadlines`.
Return the ledger link https://ledger.ainumbers.co/ so a human can re-verify without contacting us.
PII rule: All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Open the tool with the sample prefilled: https://ainumbers.co/chaingraph/art-467-dora-incident-classifier.html#p=v1.H4sIAAAAAAAA_wESAe3-eyJpbmNpZGVudF9pZCI6IklOQy0yMDI2LTAxMDAiLCJjbGFzc2lmaWNhdGlvbl9hdCI6IjIwMjYtMDctMjBUMDk6MDA6MDBaIiwiY2xpZW50c19hZmZlY3RlZF9wY3QiOjIsImR1cmF0aW9uX21pbnV0ZXMiOjMwLCJnZW9ncmFwaGljYWxfc3ByZWFkX2NvdW50cmllc19jb3VudCI6MSwiZGF0YV9sb3NzZXMiOmZhbHNlLCJlY29ub21pY19pbXBhY3RfYW1vdW50Ijo1MDAwLCJjcml0aWNhbF9zZXJ2aWNlc19hZmZlY3RlZCI6ZmFsc2UsInJlcHV0YXRpb25hbF9pbXBhY3QiOmZhbHNlfUKxhiwSAQAA