alirezarezvani/claude-skills / ra-qm-team/skills/nis2-readiness
nis2-readiness
VerifiedUse when a cyberattack, ransomware or outage hits a hospital, utility, transport, digital-infrastructure or other EU company and it must report under NIS2 (Directive 2022/2555) or the German NIS2UmsuCG/BSIG - 24h early warning, 72h notification, one-month final report. Also for whether a company is an essential or important entity, BSI registration, management-board liability and training (Article 20), an Article 21 gap analysis, or one incident that also triggers DORA, CRA or GDPR reports. Four deterministic scripts with cited articles.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.0 KB |
| assets/assessment.example.csv | other | 921 B |
| assets/entities.example.csv | other | 524 B |
| assets/incident_runbook.md | markdown | 1.5 KB |
| assets/incidents.example.csv | other | 1.3 KB |
| assets/profile.example.json | config | 489 B |
| references/article21_measures.md | markdown | 3.6 KB |
| references/incident_reporting_article23.md | markdown | 4.4 KB |
| references/scope_and_registration.md | markdown | 5.1 KB |
| scripts/art21_gap_check.py | script | 11.8 KB |
| scripts/eu_cyber_regime_router.py | script | 16.5 KB |
| scripts/nis2_incident_clock.py | script | 19.2 KB |
| scripts/nis2_scope_classifier.py | script | 19.6 KB |
references/incident_reporting_article23.md
View on GitHub# NIS2 Article 23: significant incidents and the three reports
> 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 Β· π‘ authority guidance Β· π΄ our reading, check with counsel
## What is significant (Art 23(3))
An incident is significant if it has caused or can cause **severe operational
disruption of the services or financial loss** for the entity, or has affected
or can affect **other natural or legal persons by causing considerable
material or non-material damage**. π’ Art 23(3)
For DNS, TLD, cloud, data centre, CDN, MSP, MSSP, marketplaces, search, social
networks and trust services, Implementing Regulation 2024/2690 makes this
concrete. An incident is significant if any of these holds π’ 2024/2690 Art 3(1):
- financial loss above EUR 500 000 or 5% of annual turnover, whichever is lower;
- exfiltration of trade secrets;
- death, or considerable damage to a person's health;
- successful, suspectedly malicious and unauthorised access that may cause severe disruption;
- a sector-specific threshold in Arts 5-14 (e.g. a cloud service fully unavailable for more than 30 minutes).
Recurring incidents (twice in six months, same apparent root cause) that are
significant together count as one π’ 2024/2690 Art 4. Scheduled maintenance is
not an incident for this purpose π’ 2024/2690 Art 3(2).
## The reports
| Report | Deadline | Content | Source |
|---|---|---|---|
| Early warning | within 24 h of becoming aware | suspected unlawful or malicious cause? cross-border impact? | π’ Art 23(4)(a) |
| Incident notification | within 72 h of becoming aware (24 h for trust service providers on trust-service incidents) | update, initial assessment of severity and impact, indicators of compromise | π’ Art 23(4)(b) |
| Intermediate report | on request of the CSIRT or authority | status updates | π’ Art 23(4)(c) |
| Final report | one month after the notification | detailed description, severity and impact, type of threat or root cause, mitigation applied and ongoing, cross-border impact | π’ Art 23(4)(d) |
| Progress report | instead of the final, if the incident is ongoing at one month; final then due one month after handling ends | | π’ Art 23(4)(e) |
Recipients are informed of significant incidents likely to affect their
services "without undue delay", and of measures they can take for significant
cyber threats. π’ Art 23(1)-(2)
"Becoming aware" is not the first alert: it is when the entity has reasonable
certainty a significant incident occurred π΄ (our reading; check your
authority's guidance). The scripts therefore ask for both
detection and awareness times and fall back to detection when awareness is
missing. π΄
## Overlaps for one event
| Law | Trigger | First deadline | Recipient |
|---|---|---|---|
| NIS2 | significant incident | 24 h after awareness | CSIRT or competent authority |
| DORA (financial entities, replaces NIS2 Art 23) | major ICT incident | 4 h after classification, at most 24 h after awareness | financial competent authority (copy to CSIRT if the Member State requires, DORA Art 19(1)) |
| CRA (manufacturer of the affected product) | actively exploited vulnerability or severe incident affecting the product | 24 h after awareness | coordinator CSIRT + ENISA via the SRP |
| GDPR | personal-data breach likely to result in a risk | 72 h after awareness | data protection authority (Art 33); data subjects if high risk (Art 34) |
`eu_cyber_regime_router.py` lays these clocks side by side for one entity and
one event. Who reports is set by each law; one event can create four reports. π’
## Penalties for missing a report
Failing Art 23 is a breach sanctioned under Art 34 (see the scope reference for
ceilings). Germany: BSIG Β§65. π’
## Sources
1. Directive (EU) 2022/2555, Arts 23, 34 β https://eur-lex.europa.eu/eli/dir/2022/2555/oj
2. Implementing Regulation (EU) 2024/2690, Arts 3-14 β https://eur-lex.europa.eu/eli/reg_impl/2024/2690/oj
3. Regulation (EU) 2022/2554 (DORA), Art 19 β https://eur-lex.europa.eu/eli/reg/2022/2554/oj
4. Regulation (EU) 2024/2847 (CRA), Art 14 β https://eur-lex.europa.eu/eli/reg/2024/2847/oj
5. Regulation (EU) 2016/679 (GDPR), Arts 33-34 β https://eur-lex.europa.eu/eli/reg/2016/679/oj
6. NIS2UmsuCG, BGBl. 2025 I Nr. 301 (BSIG Β§32)
7. ENISA, NIS2 technical implementation guidance for 2024/2690 (2025) π‘ β https://www.enisa.europa.eu/
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path β even casually (like "the xlsx in my downloads") β and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |