
nis2-readiness
Scope, reporting clocks, and gap checks for NIS2 and the German NIS2UmsuCG, sorted into four scripts.
- version
- 2.14.13
- GitHub stars
- 30.3K
What it does
- Adds
/cs-eu-cyber-scope,/cs-nis2-readiness, and/cs-nis2-reportcommands plus acs-nis2-officeragent - Classifies entities as essential, important, or out by sector and size, naming the supervising authority and registration duty
- Runs the Article 23 clock for the 24h early warning, 72h notification, and one-month final report, with 2024/2690 significance thresholds
- Designed for EU companies in the 18 NIS2 sectors; financial entities are referred to DORA instead
Get an EU company ready for NIS2 (Directive 2022/2555) and the German NIS2UmsuCG. Four deterministic stdlib scripts: a scope classifier that sorts entities into essential, important or out by sector and size and names the authority and registration duty; an Article 23 clock for the 24h early warning, 72h notification and one-month final report, with the Implementing Regulation 2024/2690 significance thresholds; an Article 21 gap check of 30 measures; and a router that lays NIS2, DORA, CRA and GDPR reporting clocks side by side for one event. Ships cs-nis2-officer agent, /cs-nis2-readiness, /cs-nis2-report and /cs-eu-cyber-scope commands, 3 cited references and an incident runbook.
Add marketplace
/plugin marketplace add alirezarezvani/claude-skillsRun it inside Claude Code once, then install the plugin below.
Install
/plugin install nis2-readiness@claude-code-skillsRun it inside Claude Code after adding the marketplace.
Files
Discovered from sourceNIS2 Readiness
Portability: 4 stdlib scripts, no network, nothing submitted anywhere. Fill CSVs, run, keep the output as evidence. Not legal advice. Member State transpositions differ; the national authority decides on designation and significance.
NIS2 is an entity duty, not a product duty. It catches medium and large companies in the 18 Annex I/II sectors, plus some of any size (DNS, TLD, trust services, public e-comms, sole providers). Management bodies approve and oversee the measures and can be held liable (Art 20). Germany's NIS2UmsuCG has applied since 6 December 2025: register with the BSI within three months (BSIG §33). Teams fail the same ways: they size the group instead of the entity, nobody records when they became aware, the 72-hour notification is mistaken for the last report, and DORA entities report twice.
Workflow
# 0 - One event, several laws: which clocks run and who gets what?
python scripts/eu_cyber_regime_router.py --profile assets/profile.example.json
# 1 - Scope: essential, important, or out? Which authority, which register?
python scripts/nis2_scope_classifier.py --entities assets/entities.example.csv
# 2 - Report: is an early warning, notification or final report due now?
python scripts/nis2_incident_clock.py --incidents assets/incidents.example.csv
# 3 - Measures: what blocks the Article 21 baseline?
python scripts/art21_gap_check.py --assessment assets/assessment.example.csv [--digital-provider]
Run step 2 first whenever an incident is live: it is the only step with a
24-hour deadline. --list-sectors, --list-special, --list and --template
print the Annex I/II sectors, size-independent flags and the 30 assessment ids.
The gates block on (exit 4)
- An entity with no size data: size decides essential vs important vs out (Art 2(1), Art 3; Rec 2003/361).
- A report past its deadline, or significance still unassessed 24 h after awareness (Art 23(3)-(4)).
- An Article 21 measure NOT MET, or an id left unassessed (Art 21(2)(a)-(j)).
Hard rules
- Size the entity, not the group, but count partner and linked enterprises as Rec 2003/361 does; say which figures you used.
- Awareness is evidence. No logged awareness time means the clock runs from detection.
- 72 hours is not the end. A final report is due one month after the notification; a progress report if handling is still open.
- DORA wins for financial entities (Art 4 lex specialis): route them to
dora-readiness, and check whether the Member State wants a copy to the CSIRT (DORA Art 19(1)). - Digital providers use 2024/2690. DNS, TLD, cloud, data centres, CDNs, MSPs, MSSPs, marketplaces, search, social networks and trust services: pass
--digital-providerfor the Annex section behind each measure and the Art 3 significance thresholds. - Never submit for the user. The scripts prepare; a named person reports to the CSIRT or authority (in Germany, the BSI portal).
Scripts
| Script | Role | Exit codes |
|---|---|---|
scripts/nis2_scope_classifier.py | Sector (Annex I/II), size (Rec 2003/361), essential/important (Art 3), size-independent cases (Art 2(2)), DORA overlap, jurisdiction (Art 26), registration (Art 27; BSIG §33) | 0 · 2 findings · 3 bad input · 4 blocked |
scripts/nis2_incident_clock.py | Significance (Art 23(3); 2024/2690 Arts 3-14), 24h / 72h / one-month deadlines, report content, recipients informed (Art 23(1)) | 0 on time · 2 open · 3 · 4 overdue |
scripts/art21_gap_check.py | 30 ids: governance (Art 20), Art 21(2)(a)-(j), reporting, registration; 2024/2690 Annex mapping | 0 ready · 2 gaps · 3 · 4 blocked |
scripts/eu_cyber_regime_router.py | NIS2 / DORA / CRA / GDPR for one entity and event, parallel clocks, open questions | 0 · 2 open questions · 3 |
All support --help, --sample and --output json.
References and assets
references/scope_and_registration.md— sectors, size rules, essential vs important, jurisdiction, German BSIG thresholds and §33 registration, fines (7 sources)references/incident_reporting_article23.md— significance, the three reports, 2024/2690 thresholds, overlap with DORA, CRA and GDPR (7 sources)references/article21_measures.md— each measure with typical evidence and the 2024/2690 Annex section (6 sources)assets/incident_runbook.md— standing set-up and per-incident recordassets/entities.example.csv,assets/incidents.example.csv,assets/assessment.example.csv,assets/profile.example.json— input formats
Readme
nis2-readiness
NIS2 is entity law, not product law. Germany's NIS2UmsuCG has applied since 6 December 2025: register with the BSI within three months, report significant incidents within 24 hours.
Four deterministic scripts for companies in the 18 NIS2 sectors:
| Script | Question it answers |
|---|---|
nis2_scope_classifier.py | Is each entity essential, important or out, which Member State supervises it, and must it register? |
nis2_incident_clock.py | Is an incident significant, and is the early warning, notification or final report due, overdue or late? |
art21_gap_check.py | What blocks the Article 21 baseline, measure by measure, with the 2024/2690 Annex section for digital providers? |
eu_cyber_regime_router.py | For one company and one event, which of NIS2, DORA, CRA and GDPR apply, and which clocks run in parallel? |
No network, nothing submitted. Every rule cites Directive (EU) 2022/2555, Implementing Regulation (EU) 2024/2690 or the BSIG 2025 section it implements.
Not legal advice. Member State transpositions differ, and the national authority decides on designation and significance.
Install
/plugin marketplace add alirezarezvani/claude-skills
/plugin install nis2-readiness@claude-code-skills
Use
/cs-nis2-report incidents.csv # a live incident
/cs-eu-cyber-scope profile.json # one event, several laws
/cs-nis2-readiness entities.csv incidents.csv assessment.csv # full pass
Or run the scripts directly. Each has --help, --sample and --output json:
cd skills/nis2-readiness
python scripts/nis2_scope_classifier.py --sample
python scripts/nis2_incident_clock.py --sample
python scripts/art21_gap_check.py --sample
python scripts/eu_cyber_regime_router.py --sample
What it refuses
- An entity with no headcount or financials: size decides the category.
- An Article 21 assessment that skips any of the 30 ids, or marks a mandatory measure not applicable.
- An incident with no awareness time: the clock then runs from detection.
Financial entities
DORA replaces NIS2 Articles 21 and 23 for them. Install dora-readiness.
License
MIT. See the repository LICENSE.
Details
- Marketplace
- alirezarezvani/claude-skills
- Source
- ra-qm-team/nis2-readiness
- Author
- Alireza Rezvani
- Category
- Compliance
- Keywords
- nis2, eu-2022-2555, nis2umsucg, bsig, article-23, incident-reporting, essential-entity, important-entity, article-21, bsi, cybersecurity, compliance
More from alirezarezvani/claude-skills
All 130- notebooklmv2.14.5
- patentv2.14.5
- pm-skillsv2.14.6
- power-user-coachv2.14.5
- product-managerv2.2.0
- product-skillsv2.14.11
- prompt-governancev2.14.5
- pulsev2.14.5
- pwv2.14.6
- ra-qm-skillsv2.14.14
- readme-polishv2.14.12
- reflect-skillv2.14.5
- research-ops-skillsv2.14.6
- research-orchestratorv2.14.7
- research-summarizerv2.14.5
- roastv2.14.6
- scrum-masterv2.2.0
- security-guidancev2.14.5
- self-improving-agentv2.14.11
- skill-doctorv2.14.1
- skill-retrov2.14.6
- skill-security-auditorv2.2.0
- skillopt-sleepv2.14.5
- slo-architectv2.14.5
Similar to nis2-readiness
More Security & Compliance
eccaffaan-m/everything-claude-code308.6K starsHarness-native ECC operator layer - 72 agents, 328 skills, 99 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready work
security-guidanceanthropics/claude-code156.1K starsSecurity review for Claude-generated code. Pattern-based warnings on edits, LLM-powered diff review on Stop, and an agentic commit reviewer that catches injecti
ruflo-aidefenceruvnet/ruflo82.2K starsAI safety scanning, PII detection, prompt injection defense, and adaptive threat learning
front-end-checklistthedaviddias/Front-End-Checklist74.8K starsReview frontend code and live pages against 386 quality-gated rules for accessibility, performance, SEO, security, and HTML/CSS/JS best practices.
agentic-bundle-aas-privacy-compliance-engineeringsickn33/agentic-awesome-skills50.1K starsInstall the "AAS Privacy & Compliance Engineering" editorial skill bundle for Claude Code.
42crunch-api-security-testinganthropics/claude-plugins-official47.9K starsAutomate API security directly in Claude Code with 42Crunch - automatically audit OpenAPI specs, detect vulnerabilities aligned with OWASP API Security risks (i