alirezarezvani/claude-skills / ra-qm-team/skills/dora-readiness
dora-readiness
VerifiedUse when a bank, payment or e-money institution, investment firm, insurer, crypto-asset service provider or fund manager in the EU faces DORA (Regulation 2022/2554, Digital Operational Resilience Act) - is an ICT outage or cyber incident major, when the initial (4h/24h), intermediate (72h) and final reports are due, weekends included; the register of information; ICT or cloud contracts missing audit rights, exit plans or other Article 30 terms; scope and the simplified framework for small firms. Not for DORA DevOps metrics. Three deterministic scripts with cited articles.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.1 KB |
| assets/entities.example.csv | other | 443 B |
| assets/incidents.example.csv | other | 1.0 KB |
| assets/major_incident_runbook.md | markdown | 1.4 KB |
| assets/register.example.csv | other | 758 B |
| references/major_incident_reporting.md | markdown | 4.4 KB |
| references/scope_and_proportionality.md | markdown | 3.7 KB |
| references/third_party_register_and_contracts.md | markdown | 3.8 KB |
| scripts/dora_incident_classifier.py | script | 24.1 KB |
| scripts/dora_scope_check.py | script | 13.1 KB |
| scripts/register_of_information_check.py | script | 13.4 KB |
references/major_incident_reporting.md
View on GitHub# DORA major ICT-related incidents: classification and reporting
> Rules last verified 2026-11-17 against the EUR-Lex texts cited below. Re-check before relying on a deadline or threshold.
Confidence: π’ legal text Β· π‘ ESA guidance or Q&A Β· π΄ our reading, check with counsel
## Classification (Delegated Regulation 2024/1772)
**Critical services affected (Art 6)** is the gate: the incident affects ICT
services supporting critical or important functions, or financial services
requiring authorisation, registration or supervision, or is a successful,
malicious and unauthorised access to network and information systems. π’
**Major (Art 8(1))** = critical services affected **and** either π’
- (a) a successful, malicious, unauthorised access that may result in data losses (Art 9(5)(b)); or
- (b) two or more of the other thresholds:
| Criterion | Threshold | Article |
|---|---|---|
| Clients, counterparts, transactions | >10% of clients using the service, or >100 000 clients, or >30% of counterparts, or >10% of daily average transactions by number or value, or relevant clients or counterparts affected | π’ Art 9(1) |
| Reputational impact | media coverage, repeated complaints, regulatory requirements missed, or likely client loss | π’ Art 9(2) |
| Duration and downtime | >24 h, or >2 h downtime of a service supporting a critical or important function | π’ Art 9(3) |
| Geographical spread | material impact in two or more Member States | π’ Art 9(4) |
| Data losses | adverse impact on availability, authenticity, integrity or confidentiality | π’ Art 9(5)(a) |
| Economic impact | costs and losses above EUR 100 000 | π’ Art 9(6) |
**Recurring (Art 8(2)):** incidents that are not major alone but occurred at
least twice in six months with the same apparent root cause, and together meet
Art 8(1), are one major incident. Check monthly. Not for microenterprises or
Art 16 entities. π’
## Deadlines (Delegated Regulation 2025/301 Art 5)
| Report | Deadline | |
|---|---|---|
| Initial notification | within 4 h of classifying the incident as major, and no later than 24 h after becoming aware of it | π’ Art 5(1)(a) |
| β if classified more than 24 h after awareness | 4 h after classification | π’ Art 5(2) |
| Intermediate report | within 72 h of the initial notification; updated when status changes and when regular activities are recovered | π’ Art 5(1)(b) |
| Final report | within one month of the latest updated intermediate report | π’ Art 5(1)(c) |
- **Can't make it?** Tell the competent authority before the deadline, with reasons. π’ Art 5(3)
- **Weekends and bank holidays:** submit by noon of the next working day. π’ Art 5(4)
- **Except** initial and intermediate reports of credit institutions, CCPs, trading venues, and entities identified as NIS2 essential or important. π’ Art 5(5) The authority can extend this. π’ Art 5(6)
Report formats: the ITS standard forms. π’ Implementing Regulation (EU) 2025/302
## Around the report
- **Clients:** where a major incident affects their financial interests, inform them without undue delay of the incident and the measures taken. π’ DORA Art 19(3)
- **Significant cyber threats** may be notified voluntarily. π’ DORA Art 19(2)
- **Outsourced reporting** to a third party is allowed; responsibility stays with the entity. π’ DORA Art 19(5)
- **Payment-related incidents** of credit, payment, e-money and AIS institutions are reported under DORA, no longer PSD2 Art 96. π’ DORA Art 23 and Directive 2022/2556
## What the classifier will not decide
Whether a service supports a critical or important function is your
assessment (DORA Art 3(22)); the script takes it as input. Reputational impact
and "relevant clients" are judgment calls the script records, not makes. π΄
## Sources
1. Regulation (EU) 2022/2554, Arts 17-23 β https://eur-lex.europa.eu/eli/reg/2022/2554/oj
2. Commission Delegated Regulation (EU) 2024/1772 (classification) β https://eur-lex.europa.eu/eli/reg_del/2024/1772/oj
3. Commission Delegated Regulation (EU) 2025/301 (content and time limits) β https://eur-lex.europa.eu/eli/reg_del/2025/301/oj
4. Commission Implementing Regulation (EU) 2025/302 (forms and templates) β https://eur-lex.europa.eu/eli/reg_impl/2025/302/oj
5. Directive (EU) 2022/2556 β https://eur-lex.europa.eu/eli/dir/2022/2556/oj
6. EBA, DORA incident reporting pages π‘ β https://www.eba.europa.eu/
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |