Nis2

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 7a840ef8562c · 14 Oct 2026Report an issue or request a re-scan

• PublisherSushegaad GitHub userOwner of the repository this skill is read from
• Source folderSushegaad/Claude-Skills-Governance-Risk-and-Compliance/plugins/nis2/skills/nis2The exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict7a840ef8562cA new audit runs when the source changes
• Repository statusNot archivedLast push 4 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: EU NIS2 Directive (Directive (EU) 2022/2555) compliance advisor for essential and important entities: entity classification, Art. 21 risk management measures, Art. 23 incident reporting timelines (24h/72h/1 month), Art.…

---
name: nis2
description: >
  EU NIS2 Directive (Directive (EU) 2022/2555) compliance advisor for essential and important entities: entity classification, Art. 21 risk management measures, Art. 23 incident reporting timelines (24h/72h/1 month), Art. 20 governance obligations, supply chain security (Art. 21(2)(d); coordinated risk assessments Art. 22), gap assessments, policy drafting, ISO 27001 alignment, and penalty exposure analysis. Also covers Commission Implementing Regulation (EU) 2024/2690, the technical/methodological sub-requirements for Art. 21(2) and the significant-incident thresholds binding on DNS/cloud/data-centre/MSP/MSSP/trust-service and other digital entities. Use for NIS2 readiness, transposition questions, ENISA technical implementation guidance, significant-incident thresholds, supervisory differences between essential and important entities, and cross-border coordination.
---

# NIS2 Directive Compliance Advisor

> **Last verified:** 2026-09-05

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.

## How to Respond

| Task | Output Format |
|------|--------------|
| Entity classification | Step-by-step scope + classification analysis (workflow below), ending with a clear EE / IE / out-of-scope conclusion and its supervisory consequences |
| Gap assessment | Table: Art. 21(2) measure \| Current State \| Gap \| Priority \| Recommended Action (use the template below) |
| Incident reporting | Timeline with concrete deadlines computed from the stated incident time |
| Governance (Art. 20) | Obligation checklist with board-ready framing |
| Policy drafting | Full policy document with NIS2 article mapping per section |
| Framework comparison (ISO 27001, DORA) | Mapping table + gaps + programme recommendation |
| Penalty exposure | Table citing Art. 34 with the entity's actual figures applied |

## 1. Entity Classification — Do This Carefully

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.

### Step 1 — Sector scope (Annex I / Annex II)

- **Annex I (high-criticality sectors):** energy (electricity incl. producers, DSOs, TSOs; district heating; oil; gas; hydrogen), transport (air, rail, water, road), banking, financial market infrastructure, health, drinking water, waste water, digital infrastructure (IXPs, DNS service providers, TLD registries, cloud computing service providers, data centre service providers, CDNs, trust service providers, public electronic communications networks/services), ICT service management B2B (MSPs, MSSPs), public administration, space
- **Annex II (other critical sectors):** postal/courier, waste management, chemicals, food, manufacturing (medical devices, computers/electronics, machinery, motor vehicles, other transport equipment), digital providers (online marketplaces, online search engines, social networking platforms), research organisations

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.

### Step 2 — Size threshold (Art. 2(1), SME Recommendation 2003/361)

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.

### Step 3 — Essential vs Important (Art. 3)

- **Essential Entity (EE)** = Annex I sector AND **exceeds the large-enterprise ceiling**: ≥250 employees, OR annual turnover >€50M AND balance sheet >€43M. Plus, regardless of size: qualified trust service providers, TLD registries, DNS providers; providers of public electronic communications networks/services that are at least medium-sized; central government public administration; entities designated critical under the CER Directive (EU) 2022/2557; sole providers or Member-State-designated entities.
- **Important Entity (IE)** = everything else in scope: **medium-sized Annex I entities** and all in-scope Annex II entities (unless designated essential by the 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.

### Step 4 — Jurisdiction and registration

- **Jurisdiction (Art. 26):** generally the Member State(s) where the entity is established. Exception — DNS, TLD, cloud, data centre, CDN, MSP, MSSP, and online marketplace/search/social entities fall under the Member State of th

Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
git -C Claude-Skills-Governance-Risk-and-Compliance checkout 7a840ef8562c

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 7a840ef8562c

Questions about Nis2

• github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Complianc — the audited source at commit 7a840ef8562c and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology