Skip to content

alirezarezvani/claude-skills / ra-qm-team/skills/dora-readiness

dora-readiness

Verified

Use 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.

assets/major_incident_runbook.md

View on GitHub
# DORA major ICT incident runbook

Fill the standing part once; copy the per-incident part for each incident.
Keep it with the incident record. Deadlines: Delegated Regulation (EU) 2025/301 Art 5.

## Standing set-up

| Item | Value |
|---|---|
| Competent authority and submission channel | |
| Entity kind for Art 5(5) (credit institution / CCP / trading venue / NIS2-identified / other) | |
| Copy to NIS2 CSIRT required by our Member State? (DORA Art 19(1)) | |
| Bank holidays file for `--holidays` | |
| Who classifies (name, deputy) | |
| Who submits (name, deputy) | |
| Who informs clients (DORA Art 19(3)) | |
| Register of critical or important functions (DORA Art 3(22)) | |

## Per incident

| Step | Time (with offset) | Who | Note |
|---|---|---|---|
| Detected | | | |
| Aware | | | starts the 24 h ceiling |
| Classified major | | | starts the 4 h clock; attach the criteria met |
| Initial notification sent | | | due min(classified + 4 h, aware + 24 h) |
| Clients informed | | | if financial interests affected |
| Intermediate report sent | | | due initial + 72 h |
| Regular activities recovered | | | send an updated intermediate report |
| Final report sent | | | due last intermediate + 1 month |
| Authority told of a delay (Art 5(3)) | | | before the deadline, with reasons |

Then run:

```bash
python scripts/dora_incident_classifier.py --incidents incidents.csv --entity <kind> --holidays 2026-12-25,2026-12-26
```
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 196kUpdated Claude CodeCodexVerifiedInstall