New advertisers: 50% off your first month with code FIRSTMONTHSee slots

Operational resilience checks for EU financial entities preparing for DORA, including incident reporting clocks.

version
2.14.13
GitHub stars
30.3K
View on GitHub

What it does

  • Adds 3 deterministic stdlib scripts covering scope, major-incident classification, and register of information checks
  • Covers the 20 DORA entity types, exclusions, the Article 16 simplified framework, and critical ICT provider oversight
  • Applies RTS 2024/1772 thresholds and the RTS 2025/301 reporting clock, including 4h/24h, 72h, one-month, and weekend rules
  • Includes /cs-dora-readiness, /cs-dora-incident, the cs-dora-officer agent, and a major-incident runbook for EU banks, insurers, and investment firms

Get an EU financial entity ready for DORA, the Digital Operational Resilience Act (Regulation 2022/2554). Three deterministic stdlib scripts: a scope check for the 20 entity types, exclusions, the Article 16 simplified framework and critical ICT provider oversight; a major-incident classifier that applies the Delegated Regulation 2024/1772 thresholds, catches recurring incidents and runs the 2025/301 clock (initial 4h/24h, intermediate 72h, final one month, weekend rule); and a register of information check for Article 30 contract terms, exit plans and concentration risk. Ships cs-dora-officer agent, /cs-dora-readiness and /cs-dora-incident commands, 3 cited references and a major-incident runbook.

Add marketplace

/plugin marketplace add alirezarezvani/claude-skills

Run it inside Claude Code once, then install the plugin below.

Install

/plugin install dora-readiness@claude-code-skills

Run it inside Claude Code after adding the marketplace.

Files

Discovered from source

DORA Readiness

Portability: 3 stdlib scripts, no network, nothing submitted anywhere. Fill CSVs, run, keep the output as evidence. Not legal advice. Your competent authority supervises; national transposition choices (e.g. CSIRT copies) vary.

DORA has applied since 17 January 2025 to 20 types of financial entity and to the ICT providers that serve them. Supervisors first asked for two things: the register of information and major-incident reports. Teams fail in predictable ways: they classify on gut feeling instead of the RTS thresholds, start the 4-hour clock at awareness instead of at classification, miss recurring incidents that are major together, and sign cloud contracts for critical functions with no audit right or exit plan.

Workflow

# 1 - Scope: full regime, simplified (Art 16), excluded, or ICT provider?
python scripts/dora_scope_check.py --entities assets/entities.example.csv
# 2 - Incidents: which are major, which report is due, is any overdue?
python scripts/dora_incident_classifier.py --incidents assets/incidents.example.csv --entity credit-institution
# 3 - Third parties: does the register and every contract hold up?
python scripts/register_of_information_check.py --register assets/register.example.csv

Run step 2 first whenever an ICT incident is live. --list-types, --list-exemptions, --list-simplified and --list-terms print the Art 2 entity types, exclusions, Art 16 cases and the Art 30 contract terms.

How an incident becomes major (RTS 2024/1772 Art 8)

It affects critical services (Art 6) and either a successful malicious unauthorised access that may cause data loss, or two of: clients (>10%,

100 000, >30% counterparts, >10% transactions, or relevant clients), reputation, duration (>24 h, or >2 h down on a critical function), two Member States, data impact, economic loss >EUR 100 000. Incidents with the same root cause, at least twice in six months, that meet this together are one major incident (Art 8(2)).

The gates block on (exit 4)

  1. An entity type DORA does not list, or no type at all (Art 2(1)).
  2. A report past its deadline: initial 4 h after classification and no later than 24 h after awareness; intermediate 72 h after the initial; final one month after the last intermediate (RTS 2025/301 Art 5).
  3. A contract for a critical or important function missing an Art 30(3) term or an exit plan (Art 28(8)), or a contract never assessed for criticality.

Hard rules

  • Classify against the thresholds, write the classification time down. It starts the 4-hour clock.
  • Weekend relief is narrow. Noon of the next working day applies, but not to initial and intermediate reports of credit institutions, CCPs, trading venues or NIS2-identified entities (Art 5(5)): pass --entity.
  • Late still owes the report, and the warning. Tell the authority before a deadline passes (Art 5(3)).
  • Clients hear from you. If their financial interests are hit, inform them without undue delay (DORA Art 19(3)).
  • Microenterprises and Art 16 entities skip the recurring check, not the reporting.
  • Never submit for the user. The scripts prepare; a named person files with the competent authority.

Scripts

ScriptRoleExit codes
scripts/dora_scope_check.pyEntity type (Art 2(1)(a)-(u)), exclusions (Art 2(3)), simplified framework (Art 16), microenterprise, NIS2 overlap, CTPP (Arts 31-35)0 · 2 findings · 3 bad input · 4 unplaced
scripts/dora_incident_classifier.pyArt 6/8/9 classification, recurring incidents, initial / intermediate / final deadlines, weekend rule, client notice0 on time · 2 open · 3 · 4 overdue
scripts/register_of_information_check.pyLEI, criticality, Art 30(2) and 30(3) terms, exit plan (Art 28(8)), risk assessment (Art 28(4)), concentration and third country (Art 29)0 clean · 2 gaps · 3 · 4 blocked

All support --help, --sample and --output json.

References and assets

Readme

dora-readiness

DORA has applied since 17 January 2025. Supervisors first ask for two things: the register of information and major-incident reports, the first due 4 hours after you classify the incident as major.

Three deterministic scripts for EU financial entities:

ScriptQuestion it answers
dora_scope_check.pyFull regime, simplified framework (Art 16), excluded, or ICT provider? NIS2 overlap, critical provider oversight?
dora_incident_classifier.pyIs an ICT incident major under RTS 2024/1772, are recurring incidents major together, and is a report due, overdue or late under RTS 2025/301?
register_of_information_check.pyDoes every ICT contract carry the Article 30 terms, does every critical function have an exit plan, and where is concentration risk?

No network, nothing submitted. Every rule cites Regulation (EU) 2022/2554 or the delegated or implementing regulation it implements.

Not legal advice. The competent authority supervises; contract wording goes to counsel. This is the Digital Operational Resilience Act, not DevOps DORA metrics.

Install

/plugin marketplace add alirezarezvani/claude-skills
/plugin install dora-readiness@claude-code-skills

Use

/cs-dora-incident incidents.csv                              # a live ICT incident
/cs-dora-readiness entities.csv incidents.csv register.csv   # full pass

Or run the scripts directly. Each has --help, --sample and --output json:

cd skills/dora-readiness
python scripts/dora_scope_check.py --sample
python scripts/dora_incident_classifier.py --sample
python scripts/register_of_information_check.py --sample

What it refuses

  • An entity type DORA does not list.
  • A contract for a critical or important function without the Art 30(3) terms or an exit plan.
  • A contract nobody assessed for criticality.

Non-financial entities

Install nis2-readiness; it also routes one event across NIS2, DORA, CRA and GDPR.

License

MIT. See the repository LICENSE.

Details

Marketplace
alirezarezvani/claude-skills
Source
ra-qm-team/dora-readiness
Author
Alireza Rezvani
Category
Compliance
Keywords
dora, digital-operational-resilience-act, eu-2022-2554, major-ict-incident, register-of-information, ict-third-party, article-30, financial-entities, ict-risk, incident-reporting, compliance

More from alirezarezvani/claude-skills

All 130

Similar to dora-readiness

More Security & Compliance