/eu-nis2-expert
EU NIS2 Directive (Directive (EU) 2022/2555) expert. Reference-depth knowledge of essential vs important entity classification, Article 20 governance, the Article 21 ten cybersecurity risk-management measures, the Article 23 24h/72h/1mo incident-reporting timeline, and
$ npx -y skills add GRCEngClub/claude-grc-engineering --skill eu-nis2-expert --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/eu-nis2-expert
Context preview
The summary Claude sees to decide when to auto-load this skill.
EU NIS2 Directive (Directive (EU) 2022/2555) expert. Reference-depth knowledge of essential vs important entity classification, Article 20 governance, the Article 21 ten cybersecurity risk-management measures, the Article 23 24h/72h/1mo incident-reporting timeline, and
SKILL.md
eu-nis2-expert.SKILL.mdname: eu-nis2-expert
description: EU NIS2 Directive (Directive (EU) 2022/2555) expert. Reference-depth knowledge of essential vs important entity classification, Article 20 governance, the Article 21 ten cybersecurity risk-management measures, the Article 23 24h/72h/1mo incident-reporting timeline, and supervision/enforcement under Articles 32-34. SCF-backed gap assessment via the crosswalk.
allowed-tools: Read, Glob, Grep, Write
EU NIS2 Directive Expert
Reference-depth expertise for the **EU NIS2 Directive** — Directive (EU) 2022/2555 of the European Parliament and of the Council of 14 December 2022 on measures for a high common level of cybersecurity across the Union. NIS2 repealed the original NIS Directive (Directive (EU) 2016/1148) and entered into force on 16 January 2023, with a transposition deadline of 17 October 2024.
This plugin bundles the SCF crosswalk (68 SCF controls → 30 NIS2 directive-level controls) with directive-specific scoping, governance, evidence, and incident-reporting context. Detailed technical and organisational measures from Article 21 are elaborated in the NIS2 implementing acts (Commission Implementing Regulation (EU) 2024/2690 for digital infrastructure / DNS / TLD / cloud / data centre / CDN / managed service / managed security / online marketplace / search engine / social networking entities — known here as "the Annex"); a parallel SCF mapping `emea-eu-nis2-annex-2024` covers the 351-control breakdown of those technical measures.
Framework identity
- **Instrument**: Directive (EU) 2022/2555 (NIS2). A *Directive*, not a Regulation — Member States transpose it into national law.
- **Predecessor**: NIS1 (Directive (EU) 2016/1148), repealed by Article 44 of NIS2.
- **Entry into force**: 16 January 2023.
- **Transposition deadline**: 17 October 2024. As of late 2025–early 2026, transposition status varies sharply by Member State; some states (Germany's NIS2UmsuCG, Belgium's NIS2 law, Italy's Decreto Legislativo n. 138/2024) had national laws in force on or near time, several others were delayed and ran (or are still running) Commission infringement procedures.
- **SCF framework ID**: `emea-eu-nis2-2022` (directive). Companion: `emea-eu-nis2-annex-2024` (Implementing Regulation 2024/2690 technical measures).
- **Region**: EMEA (EU + EEA where applicable through joint committee decisions).
- **Direct enforcement**: No. NIS2 is enforced by each Member State's national competent authority via that state's transposition law. ENISA coordinates EU-wide and runs the CSIRTs Network and EU-CyCLONe.
- **Affected sectors**: 18 categories grouped into Annex I (essential) and Annex II (important) — see "Sectoral scope" below.
- **Penalty exposure**: Administrative fines whose national maximums must be at least **€10 million or 2% of total worldwide annual turnover** (essential entities) and at least **€7 million or 1.4% of total worldwide annual turnover** (important entities), whichever is higher, per Article 34. Member States may set higher national maximums.
Framework in plain language
NIS2 is the EU's baseline cybersecurity law for organisations that run critical or important services. It does four things at once:
1. Expands NIS1's scope from a small list of "operators of essential services" and "digital service providers" to roughly 18 sectors covering most medium and large organisations in critical supply chains (energy, transport, healthcare, drinking water, wastewater, banking, financial market infrastructure, digital infrastructure, ICT service management, postal services, manufacturing of medical devices and machinery, digital providers, food, chemicals, waste, public administration, research, space). 2. Imposes a **harmonised baseline of cybersecurity risk-management measures** on in-scope entities (the ten Article 21 domains). 3. Imposes a **harmonised incident-reporting regime** with a 24-hour early warning, a 72-hour incident notification, and a 1-month final report (Article 23). 4. Introduces **management-body accountability** (Article 20): the management body of an in-scope entity must approve cybersecurity risk-management measures, oversee their implementation, and undergo regular cybersecurity training. National laws may attach personal liability to management-body members for serious failures.
NIS2 is jurisdictionally uneven. Because it is a Directive, the substantive rules a regulator can enforce against you are in your Member State's transposition law, not in NIS2 itself. The directive defines a floor; many Member States layer additional national requirements on top (mandatory CISO appointments, registration deadlines, sectoral rules, sector-specific reporting portals). This plugin focuses on the directive-level baseline that all Member State laws must implement; national specifics are downstream.
Sectoral scope and entity classification
NIS2 applies a **size-based threshold** combined with a **sector list**, with carve-outs that pull smaller organisations in.
Step 1: Sector check (Annex I or Annex II?)
**Annex I — high-criticality sectors (default classification: essential)**:
- **Energy** — electricity, district heating and cooling, oil, gas, hydrogen
- **Transport** — air, rail, water, road
- **Banking** — credit institutions
- **Financial market infrastructures** — trading venues, central counterparties
- **Health** — healthcare providers, EU reference laboratories, R&D entities for medicinal products, manufacturers of basic pharmaceutical products and preparations, manufacturers of critical medical devices
- **Drinking water** — suppliers and distributors of water intended for human consumption
- **Wastewater** — wastewater collection, disposal, treatment undertakings
- **Digital infrastructure** — IXPs, DNS service providers (excluding root servers), TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, trust service providers, providers of p
Read more
name: eu-nis2-expert description: EU NIS2 Directive (Directive (EU) 2022/2555) expert. Reference-depth knowledge of essential vs important entity classification, Article 20 governance, the Article 21 ten cybersecurity risk-management measures, the Article 23 24h/72h/1mo incident-reporting timeline, and supervision/enforcement under Articles 32-34. SCF-backed gap assessment via the crosswalk. allowed-tools: Read, Glob, Grep, Write
EU NIS2 Directive Expert
Reference-depth expertise for the **EU NIS2 Directive** — Directive (EU) 2022/2555 of the European Parliament and of the Council of 14 December 2022 on measures for a high common level of cybersecurity across the Union. NIS2 repealed the original NIS Directive (Directive (EU) 2016/1148) and entered into force on 16 January 2023, with a transposition deadline of 17 October 2024.
This plugin bundles the SCF crosswalk (68 SCF controls → 30 NIS2 directive-level controls) with directive-specific scoping, governance, evidence, and incident-reporting context. Detailed technical and organisational measures from Article 21 are elaborated in the NIS2 implementing acts (Commission Implementing Regulation (EU) 2024/2690 for digital infrastructure / DNS / TLD / cloud / data centre / CDN / managed service / managed security / online marketplace / search engine / social networking entities — known here as "the Annex"); a parallel SCF mapping `emea-eu-nis2-annex-2024` covers the 351-control breakdown of those technical measures.
Framework identity
- **Instrument**: Directive (EU) 2022/2555 (NIS2). A *Directive*, not a Regulation — Member States transpose it into national law.
- **Predecessor**: NIS1 (Directive (EU) 2016/1148), repealed by Article 44 of NIS2.
- **Entry into force**: 16 January 2023.
- **Transposition deadline**: 17 October 2024. As of late 2025–early 2026, transposition status varies sharply by Member State; some states (Germany's NIS2UmsuCG, Belgium's NIS2 law, Italy's Decreto Legislativo n. 138/2024) had national laws in force on or near time, several others were delayed and ran (or are still running) Commission infringement procedures.
- **SCF framework ID**: `emea-eu-nis2-2022` (directive). Companion: `emea-eu-nis2-annex-2024` (Implementing Regulation 2024/2690 technical measures).
- **Region**: EMEA (EU + EEA where applicable through joint committee decisions).
- **Direct enforcement**: No. NIS2 is enforced by each Member State's national competent authority via that state's transposition law. ENISA coordinates EU-wide and runs the CSIRTs Network and EU-CyCLONe.
- **Affected sectors**: 18 categories grouped into Annex I (essential) and Annex II (important) — see "Sectoral scope" below.
- **Penalty exposure**: Administrative fines whose national maximums must be at least **€10 million or 2% of total worldwide annual turnover** (essential entities) and at least **€7 million or 1.4% of total worldwide annual turnover** (important entities), whichever is higher, per Article 34. Member States may set higher national maximums.
Framework in plain language
NIS2 is the EU's baseline cybersecurity law for organisations that run critical or important services. It does four things at once:
1. Expands NIS1's scope from a small list of "operators of essential services" and "digital service providers" to roughly 18 sectors covering most medium and large organisations in critical supply chains (energy, transport, healthcare, drinking water, wastewater, banking, financial market infrastructure, digital infrastructure, ICT service management, postal services, manufacturing of medical devices and machinery, digital providers, food, chemicals, waste, public administration, research, space). 2. Imposes a **harmonised baseline of cybersecurity risk-management measures** on in-scope entities (the ten Article 21 domains). 3. Imposes a **harmonised incident-reporting regime** with a 24-hour early warning, a 72-hour incident notification, and a 1-month final report (Article 23). 4. Introduces **management-body accountability** (Article 20): the management body of an in-scope entity must approve cybersecurity risk-management measures, oversee their implementation, and undergo regular cybersecurity training. National laws may attach personal liability to management-body members for serious failures.
NIS2 is jurisdictionally uneven. Because it is a Directive, the substantive rules a regulator can enforce against you are in your Member State's transposition law, not in NIS2 itself. The directive defines a floor; many Member States layer additional national requirements on top (mandatory CISO appointments, registration deadlines, sectoral rules, sector-specific reporting portals). This plugin focuses on the directive-level baseline that all Member State laws must implement; national specifics are downstream.
Sectoral scope and entity classification
NIS2 applies a **size-based threshold** combined with a **sector list**, with carve-outs that pull smaller organisations in.
Step 1: Sector check (Annex I or Annex II?)
**Annex I — high-criticality sectors (default classification: essential)**:
- **Energy** — electricity, district heating and cooling, oil, gas, hydrogen
- **Transport** — air, rail, water, road
- **Banking** — credit institutions
- **Financial market infrastructures** — trading venues, central counterparties
- **Health** — healthcare providers, EU reference laboratories, R&D entities for medicinal products, manufacturers of basic pharmaceutical products and preparations, manufacturers of critical medical devices
- **Drinking water** — suppliers and distributors of water intended for human consumption
- **Wastewater** — wastewater collection, disposal, treatment undertakings
- **Digital infrastructure** — IXPs, DNS service providers (excluding root servers), TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, trust service providers, providers of p
Showing the first part of this file.
Open-source GRC Engineering resource for Claude. claude-grc-engineering turns technical evidence from cloud, SaaS, code, and security tools into framework-aligned findings, gap reports, remediation guidance, evidence packages, and OSCAL workflows.
Repo: GRCEngClub/claude-grc-engineering
Other skills on trust-center.
- /academic-research-companion
Guide a research project through the full academic lifecycle — from raw idea to concrete research question, literature grounding, methodology, writing, feedback, and publication. Use this skill whenever the user shares a research idea, asks to "flesh out" a topic, wants sources
Open skill - /aws-inspector-expert
Expertise in evaluating AWS accounts for compliance — what checks are meaningful, which SCF controls they map to, and how to interpret aws CLI output.
Open skill - /azure-inspector-expert
Expertise in evaluating Azure subscription findings from azure-inspector and mapping them to SCF controls.
Open skill - /crowdstrike-inspector-expert
Interpret CrowdStrike Falcon findings for sensor coverage, policy visibility, and host group scoping.
Open skill - /datadog-inspector-expert
Interpret datadog-inspector findings and translate Datadog monitoring, audit, log-retention, SSO, and RBAC results into GRC evidence and remediation.
Open skill - /drata-inspector-expert
Interpret drata-inspector findings generated from drata-cli workflows and turn Drata control, monitor, evidence, personnel, and integration posture into GRC action.
Open skill

