What Is NIS2? Who It Applies To and What It Requires
On this page
The first question most organizations ask about NIS2 is simple: are we in scope? The answer is often less obvious than it looks. A chemical plant may be in. A machine shop with the same headcount may not be. A small water utility may be pulled in by its national government, even though it is under the size threshold.
NIS2 is the European Union's main cybersecurity law for organizations that keep society and the economy running.[1] It covers energy, transport, water, health, manufacturing and many other sectors. Most of those sectors run industrial control systems and other operational technology (OT).
This article explains what NIS2 is, who it applies to, and what it requires. It then looks at what NIS2 means for industrial operators, and why its approach to risk points toward measuring cyber risk in money.
What NIS2 is
NIS2 is Directive (EU) 2022/2555. NIS refers to the security of network and information systems. The law sets a common, high level of cybersecurity across the EU for organizations whose disruption would hurt society or the economy.[1]
NIS2 replaced the first NIS Directive from 2016. The European Commission found four problems with the old law. Businesses had weak cyber resilience. Resilience varied widely between countries and sectors. Countries lacked a shared understanding of threats. And there was no joint response to a large crisis.[2] NIS2 answers these with broader scope, clearer duties, stronger supervision and common penalties.
NIS2 is a directive, not a regulation. A regulation applies directly in every EU country. A directive sets goals, and each country writes its own law to meet them. NIS2 is also a floor, not a ceiling: countries may set stricter rules.[1]
This matters in practice. The EU text decides who is broadly in scope and what the core duties are. National law decides the details, such as which authority supervises you, how you register, and where you send incident reports. An organization that operates in several EU countries must follow each country's law.
Who NIS2 applies to
NIS2 scope starts with what an organization does, then how big it is. Three tests decide most cases: sector, size and special status.
Sector. NIS2 lists 18 sectors in two annexes.[1] Annex I holds the "sectors of high criticality." Annex II holds "other critical sectors." Each sector names specific types of entity, so the real service matters, not the company's label.
| Annex | Sectors | Examples of OT-heavy entities |
|---|---|---|
| I (high criticality) | Energy, transport, banking, financial market infrastructures, health, drinking water, waste water, digital infrastructure, ICT service management, public administration, space | Power producers and grid operators, gas and oil pipelines, district heating, hydrogen plants, airports, rail infrastructure, ports, water and waste water utilities, pharmaceutical manufacturers |
| II (other critical) | Postal and courier, waste management, chemicals, food, manufacturing, digital providers, research | Chemical producers, industrial food processors, makers of electronics, electrical equipment, machinery, motor vehicles and other transport equipment |
Manufacturing is not covered as a whole. Only the listed product groups are in scope, such as electrical equipment and machinery.[1]
Size. By default, NIS2 covers medium-sized and larger organizations.[1] It uses the EU's definition of small and medium-sized enterprises.[3] An organization is medium-sized or larger if it has 50 or more staff, or if its annual turnover and balance sheet are both above €10 million. Staff and money from linked companies in the same group count toward these totals. A small plant owned by a large group is usually treated as large.
Special status. Some organizations are in scope at any size. They include telecom providers, trust service providers, domain name registries and DNS providers, and entities designated as "critical entities" under the EU's Critical Entities Resilience (CER) Directive.[1] A country may also bring in a smaller organization. Examples are the sole provider of an essential service in that country, or an organization whose disruption could seriously affect public safety, security or health.[1]
Suppliers. Many suppliers are not regulated by NIS2 directly. They still feel it. In-scope organizations must manage supply-chain security, so they pass security terms down through contracts.[1]
A quick scope check
- Does any service you provide in the EU match a sector and entity type in Annex I or II?
- Counting your whole group, do you have 50 or more staff, or turnover and balance sheet both above €10 million?
- If not, are you in a category covered at any size, or could your national government designate you?
- Does a sector-specific EU law with equivalent rules apply instead? For banks and other financial entities, that is usually the Digital Operational Resilience Act (DORA).[4]
A "yes" to 1 and 2, or to 3, and a "no" to 4, usually means you are in scope. Confirm the answer against the national law of each country where you operate.
Essential and important entities
NIS2 sorts in-scope organizations into two classes: essential entities and important entities.[1] The labels sound like a ranking of duties. They are not. Both classes must meet the same security and reporting rules.
The difference is how closely they are watched and how much they can be fined.
| Essential entities | Important entities | |
|---|---|---|
| Who, in general | Large organizations in Annex I sectors, some categories at any size, critical entities under CER, and others a country designates | Other in-scope organizations, including medium-sized Annex I entities and Annex II entities |
| Security and reporting duties | Articles 20, 21 and 23 | The same |
| Supervision | Proactive: inspections, regular and targeted audits, security scans, requests for evidence | After the fact: triggered by evidence or signs of non-compliance |
| Maximum fine | At least €10 million or 2% of worldwide annual turnover, whichever is higher | At least €7 million or 1.4% of worldwide annual turnover, whichever is higher |
A common mistake is to assume every Annex I organization is essential. A medium-sized power producer, for example, is usually an important entity. A large food processor in Annex II is also important, unless its country designates it as essential.[1]
What NIS2 requires
NIS2's duties sit in three articles: governance, risk management and incident reporting.
Management is accountable (Article 20)
The management body, usually the board or executive team, must approve the organization's cybersecurity risk-management measures and oversee how they are carried out. Its members can be held liable when the organization fails to comply.[1] They must also take training, so they can identify risks and judge how well risk is managed and what it means for the services they provide.[1] Cybersecurity can no longer sit only with the CISO.
Ten minimum measures (Article 21)
Organizations must take "appropriate and proportionate technical, operational and organisational measures" to manage risk and limit the impact of incidents.[1] The measures follow an "all-hazards approach," which considers all types of hazard, cyber and physical, and protects systems and their physical surroundings. At minimum, they cover:
- Risk analysis and information security policies
- Incident handling
- Business continuity, including backups, disaster recovery and crisis management
- Supply-chain security, including relationships with direct suppliers
- Security when buying, developing and maintaining systems, including handling and disclosing vulnerabilities
- Policies to assess whether the measures actually work
- Basic cyber hygiene and cybersecurity training
- Cryptography and, where appropriate, encryption
- Human resources security, access control and asset management
- Multi-factor authentication and secured communications, where appropriate
NIS2 says what to cover, not which framework to use. Standards such as ISO/IEC 27001 and, in industrial settings, ISA/IEC 62443 can help meet these duties.
Report significant incidents in stages (Article 23)
An incident is "significant" if it causes, or could cause, severe disruption to services or financial loss for the organization. It is also significant if it causes, or could cause, considerable damage to others.[1] Significant incidents are reported to the national computer security incident response team (CSIRT) or authority in stages:[1]
| Deadline | Report | What it covers |
|---|---|---|
| Within 24 hours of becoming aware | Early warning | Is a malicious act suspected? Could it spread across borders? |
| Within 72 hours of becoming aware | Incident notification | First assessment of severity and impact, and signs of compromise if known |
| Within one month of the notification | Final report | Full description, root cause, actions taken and cross-border impact |
The law adds a useful reassurance: the act of reporting does not, on its own, increase the organization's liability.[1]
Enforcement and penalties
National authorities enforce NIS2. Their tools range from warnings and binding instructions to orders to fix gaps, audits, and public disclosure of a breach of the rules.[1]
Fines are set by national law, but NIS2 sets a minimum for the maximum. For essential entities, the ceiling must be at least €10 million or 2% of worldwide annual turnover, whichever is higher. For important entities, it is at least €7 million or 1.4%.[1] Turnover is usually counted at the level of the whole company group.
NIS2 also reaches people, not just companies. Under national law, managers can be held personally liable for failing to ensure compliance. For essential entities that ignore orders, an authority can ask for a temporary ban that stops a chief executive or legal representative from exercising management functions in that entity.[1] When deciding on enforcement, authorities weigh the damage caused, including financial or economic loss.[1]
NIS2 in industrial (OT) environments
NIS2 never uses the term "operational technology." It does not need to. Its definition of a network and information system includes "any device or group of interconnected or related devices" that processes digital data automatically.[1] In practice, that covers controllers, safety systems, human-machine interfaces and the networks that link them. The all-hazards approach also asks organizations to protect the physical environment of their systems.
The EU's own data shows where industrial operators struggle. The EU Agency for Cybersecurity (ENISA) finds that operational technology in energy is held back by legacy systems, limited visibility and remote access. It also reports that many transport companies still leave OT out of their security assessments, and that water utilities depend heavily on legacy OT.[5] In its survey of organizations covered by NIS2, legacy systems and OT limits were the most cited barrier to compliance. Patching was the hardest requirement to meet, and many organizations took a month or more to patch critical systems.[6]
Several of the ten measures look different in a plant:
- Vulnerability handling. Patches often wait for a planned outage. Compensating controls, such as network segmentation, must carry the risk in between.
- Supply chain. Equipment makers and integrators often hold remote access to control systems. That access is part of supply-chain security.
- Business continuity. Recovery means more than restoring servers. It includes controller backups, spare parts and the ability to run the process by hand.
- Multi-factor authentication and encryption. NIS2 asks for these "where appropriate." Older industrial protocols and shared operator accounts make that judgment a real engineering decision.
The threat is not hypothetical. At the end of 2025, attackers struck more than 30 wind and solar farms and a combined heat and power plant in Poland. Remote terminal units were damaged and the farms lost contact with the grid operator, although power and heat kept flowing.[7]
Other EU laws sit beside NIS2 for industrial operators. Larger electricity operators that affect cross-border power flows also face a network code on cybersecurity.[8] Critical entities must also meet the CER Directive's rules on resilience against non-cyber risks.[9] Makers of connected industrial products face the Cyber Resilience Act.[10]
Why NIS2 points toward measuring risk in money
NIS2 defines risk the way risk quantification does. In the law, risk is "the potential for loss or disruption caused by an incident," expressed as a combination of the magnitude of that loss and the likelihood of the incident.[1] In plain terms, that is probability (frequency) and severity (magnitude).
The same idea runs through the duties. Measures must be proportionate. Proportionality is judged by the organization's exposure, its size, and "the likelihood of occurrence of incidents and their severity, including their societal and economic impact."[1] Financial loss is one test of whether an incident is significant enough to report. For digital service providers, EU rules set that line at a direct loss above €500,000 or 5% of annual turnover, whichever is lower.[11]
NIS2 does not require anyone to put a number on risk. Qualitative ratings, such as high, medium and low, remain common.[12] But a board that must approve measures, and show they are proportionate, is better served by answers in money: how much loss is likely, how bad a severe year could be, and how much each measure reduces it.
For OT, that is hard to do from history alone. Serious industrial cyber incidents are rare, public loss data is thin, and insurers have limited actuarial data. Simulation is the practical way to understand rare but catastrophic losses.
DeNexus™ leads research in OT cyber risk quantification, as the pacesetter in the field. DeRISK™ CRQ models how cyber incidents turn into operational and financial loss at industrial sites, and how controls reduce both probability and severity. That gives NIS2 programs a common language for the board, the regulator and the insurer.
This article summarizes EU law for educational purposes. It is not legal advice. Check the national law and authority guidance that apply to your organization.
Show your board what each NIS2 measure is worth
DeRISK CRQ puts OT cyber risk in financial terms boards, CISOs and CFOs act on, and shows how much each control reduces it. No OT network data needed to start.
See DeRISK CRQ in actionRelated Reading
References
- [1]
European Parliament and Council of the European Union, "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 (NIS 2 Directive)." Official Journal of the European Union, L 333, 27 Dec. 2022, pp. 80–152. URL: https://eur-lex.europa.eu/eli/dir/2022/2555/oj/eng
- [2]
European Commission, "Directive on Measures for a High Common Level of Cybersecurity across the Union (NIS2 Directive): FAQs." Shaping Europe's Digital Future. URL: https://digital-strategy.ec.europa.eu/en/faqs/directive-measures-high-common-level-cybersecurity-across-union-nis2-directive-faqs
- [3]
European Commission, "Commission Recommendation of 6 May 2003 Concerning the Definition of Micro, Small and Medium-Sized Enterprises (2003/361/EC)." Official Journal of the European Union, L 124, 20 May 2003, pp. 36–41.
- [4]
European Commission, "Commission Guidelines on the Application of Article 4(1) and (2) of Directive (EU) 2022/2555 (NIS 2 Directive)." Official Journal of the European Union, C series, 18 Sept. 2023. URL: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:52023XC0918(01)
- [5]
European Union Agency for Cybersecurity (ENISA), ENISA NIS360 2026. ENISA, May 2026. URL: https://www.enisa.europa.eu/sites/default/files/2026-05/ENISA%20NIS360%202026.pdf
- [6]
European Union Agency for Cybersecurity (ENISA), NIS Investments 2025: Main Report. ENISA, Dec. 2025. URL: https://www.enisa.europa.eu/sites/default/files/2026-02/NIS%20Investments%202025%20-%20Main%20report.pdf
- [7]
CERT Polska, "Energy Sector Incident Report 2025." CERT Polska, 30 Jan. 2026. URL: https://cert.pl/en/posts/2026/01/incident-report-energy-sector-2025/
- [8]
European Union Agency for the Cooperation of Energy Regulators (ACER), "Cybersecurity Network Code for Electricity." ACER. URL: https://www.acer.europa.eu/electricity/cybersecurity-network-code
- [9]
European Parliament and Council of the European Union, "Directive (EU) 2022/2557 on the Resilience of Critical Entities." Official Journal of the European Union, L 333, 27 Dec. 2022. URL: https://eur-lex.europa.eu/eli/dir/2022/2557/oj
- [10]
European Parliament and Council of the European Union, "Regulation (EU) 2024/2847 on Horizontal Cybersecurity Requirements for Products with Digital Elements (Cyber Resilience Act)." Official Journal of the European Union, 2024. URL: https://eur-lex.europa.eu/eli/reg/2024/2847/oj
- [11]
European Commission, "Commission Implementing Regulation (EU) 2024/2690 of 17 October 2024 Laying Down Rules for the Application of Directive (EU) 2022/2555 [...]." Official Journal of the European Union, L series, 2024. URL: https://eur-lex.europa.eu/eli/reg_impl/2024/2690/oj/eng
- [12]
Ruohonen, Jukka, et al., "Risks and Compliance with the EU's Core Cyber Security Legislation." arXiv, 2025. URL: https://arxiv.org/abs/2508.21386