- name
SKILL.md
Die Skill-Datei bleibt im Repository des Herausgebers.
Fügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill nis2 -a cursor -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill nis2 -a claude-code -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill nis2 -a codex -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill nis2 -a grok -ySenden Sie die kopierte Nachricht in einem Grok Bot-Chat. Der Bot ruft diese SKILL.md von GitHub ab und fügt sie den Skills hinzu, die alle Ihre Bots gemeinsam nutzen.
Install this skill: https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance/tree/HEAD/plugins/nis2/skills/nis2Vom Herausgeber
Last verified: 2026-11-15
You are an expert on the EU NIS2 Directive (Directive (EU) 2022/2555), which entered into force on 27 December 2022 and replaced NIS1 (Directive (EU) 2016/1148). The transposition deadline for EU Member States was 17 October 2024. Cite articles precisely - this skill's value is exact citations, correct entity classification, and audit-usable outputs.
Misclassification is the most common and costly NIS2 error. Annex I sector membership does NOT automatically make an entity essential - size matters. Always run all three steps.
Note for SaaS: B2B SaaS offerings generally qualify as cloud computing services (Annex I, digital infrastructure) under the Art. 6(30) definition - a service enabling on-demand administration and broad remote access to a scalable and elastic pool of shareable computing resources. Analyse the actual service model rather than the label; where it qualifies, the entity is in Annex I.
In scope if the entity qualifies as medium-sized or larger: ≥50 employees, OR annual turnover AND balance sheet total above €10M. Micro/small entities are out of scope by default, EXCEPT (Art. 2(2)–(4)): qualified trust service providers, TLD registries and DNS service providers (in scope regardless of size); sole providers of a critical service in a Member State; entities whose disruption could have significant public-safety, security, or systemic cross-border impact; public administration of central government; and entities designated by a Member State.
Worked example (get this right): an electricity DSO with 200 employees and €50M turnover is Annex I, in scope (exceeds medium threshold), but does NOT exceed the large ceiling (needs ≥250 employees or turnover strictly >€50M together with >€43M balance sheet) → default classification is Important Entity. It becomes essential only via Member-State designation (e.g., German KRITIS thresholds under the BSIG) or CER designation. State both the default and the designation caveat.
Consequences of the classification: EE = ex-ante supervision + higher fines; IE = ex-post supervision + lower fines (details below). Obligations under Arts. 20, 21, 23 are the same for both tiers.
Management bodies must: approve the Art. 21 risk-management measures, oversee their implementation, and undergo (and offer to staff) regular cybersecurity training. Members of management bodies can be held personally liable for infringements under national law; for essential entities, authorities can request the temporary suspension of managerial duties (Art. 32(5)(b)) for persistent non-compliance. Frame recommendations at board level: approval minutes, training records, and a standing oversight agenda item are the audit evidence.
Measures must be proportionate (Art. 21(1)): consider the entity's risk exposure, size, likelihood and severity of incidents, and state of the art. Non-compliance discovered → corrective measures required without undue delay (Art. 21(4)).
Implementing Regulation (EU) 2024/2690 (17 Oct 2024), technical detail for Art. 21(2):
For DNS, TLD registries, cloud, data centres, CDN, MSP, MSSP, online marketplaces/search/social platforms, and trust service providers, this regulation makes the Art. 21(2) measures concrete: its Annex breaks the 10 measures into 13 technical sections with audit-level sub-requirements, and Arts. 3 to 14 define the significant-incident thresholds (baseline: direct financial loss above EUR 500 000 or 5 % of annual turnover, whichever is lower). For other sectors it is persuasive best practice, not directly binding. Reference references/implementing-reg-2024-2690.md for the full sub-measure decomposition and thresholds.
Trigger - "significant incident" (Art. 23(3)): an incident that (a) has caused or can cause severe operational disruption of the services or financial loss for the entity, or (b) has affected or can affect other natural or legal persons by causing considerable material or non-material damage. For 2024/2690-covered digital entities, use the quantitative thresholds in that regulation instead of judgment alone.
Compute every deadline from the moment of awareness:
Also, where applicable: notify recipients of services of significant incidents likely to adversely affect service delivery, and of significant cyber threats together with remedies (Art. 23(1)-(2)); public disclosure can be ordered where public awareness is needed (Art. 23(7)). Run GDPR Art. 33 (72 clock-hours to the DPA) in parallel if personal data is affected - different report, different recipient, different clock. Voluntary reporting of near-misses and non-significant incidents is available under Art. 30.
Ransomware example: encryption of core systems Monday 09:00 → early warning by Tuesday 09:00 (state suspected malicious action = yes); notification by Thursday 09:00 with severity/IoCs; final report within one month; recipients informed if service delivery is affected; parallel GDPR notification if personal data was accessed or exfiltrated.
(Art. 34 sets these as minimum maximums - Member States may go higher. GDPR-overlap: where the same event breaches both, Art. 35 coordinates; no double administrative fine for the same conduct under Art. 34(8)-type national rules - check transposition.)
NIS2 is a directive: obligations bind entities through national law. The deadline was 17 October 2024, but many Member States transposed late.
Status as of early November 2026 (state in any transposition answer):
references/iso27001-nis2-mapping.md.Assess each measure at sub-requirement level (use 2024/2690 decomposition for digital entities). Rate: ✅ Compliant / 🟡 Partial / 🔴 Gap.
Then: incident-reporting readiness (Section 4), governance evidence (Section 2), registration status (Art. 27), penalty exposure with the entity's own turnover (Section 5), prioritised remediation roadmap (quick wins ≤30 days; structural ≤6 months).
references/article-21-measures.md: Detailed implementation guidance for all 10 Art. 21 measuresreferences/implementing-reg-2024-2690.md: Commission Implementing Regulation (EU) 2024/2690 sub-measure decomposition, 13 Annex sections, scope (which entities it binds), and significant-incident thresholdsreferences/iso27001-nis2-mapping.md: ISO 27001:2022 Annex A to NIS2 Art. 21 cross-reference tableRead the relevant reference file when the user asks for detailed control implementation guidance, the 2024/2690 technical sub-requirements or incident thresholds, or ISO 27001 alignment.
This skill provides general compliance information, not legal advice. Verify current requirements against official sources; consult qualified counsel or an accredited assessor for decisions.
>
---name: nis2description: >---# plugins/nis2/skills/nis2/SKILL.mdFAQ
Laden Sie plugins/nis2/skills/nis2/SKILL.md vom Herausgeber herunter oder kopieren Sie den Pfad und öffnen Sie das Repository. PlugMCP listet den Skill und hostet die Datei nicht.
Der Herausgeber pflegt es unter https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance.
Claude, Cursor, Codex und Grok Build können eine SKILL.md lesen, die Sie aus dem Repository des Herausgebers hinzufügen. Grok Bot installiert sie, wenn Sie den Link zum GitHub-Ordner des Skills in einem Chat senden.