Skip to content
-
Subscribe to our newsletter & never miss our best posts. Subscribe Now!
  • https://www.facebook.com/
  • https://twitter.com/
  • https://t.me/
  • https://www.instagram.com/
  • https://youtube.com/
Cloud Security Tips Cloud Security Tips

What is cloud security

Cloud Security Tips Cloud Security Tips

What is cloud security

  • Home
  • About us
  • Contact us
  • Home
  • About us
  • Contact us
Subscribe
Close

Search

Digital illustration of enterprise data security with a glowing blue dome protecting data, representing a security classification guide for Public, Internal, Confidential and Restricted information
Security Tips

NIS2 Directive: What It Is, Who Must Comply and Key Requirements

By admin
November 9, 2026 9 Min Read
1

The NIS2 Directive is the European Union’s most far-reaching cybersecurity law to date. It sets binding security and incident-reporting duties for thousands of organisations across energy, transport, health, finance, digital infrastructure and many other sectors — and it makes senior management personally responsible for getting it right. If your organisation operates in the EU, supplies an EU organisation, or provides a digital service used in the EU, NIS2 probably affects you, directly or through your customers’ contracts.

This guide explains what NIS2 is, who must comply, the key requirements, the penalties for getting it wrong, and a practical step-by-step path to compliance.

Table of Contents

Toggle
  • What Is the NIS2 Directive?
  • NIS vs NIS2: What Changed?
  • Who Must Comply with NIS2?
    • Essential Entities
    • Important Entities
  • The 10 Minimum Measures: NIS2 Key Requirements
  • Incident Reporting Under NIS2
  • Penalties and Management Liability
  • NIS2 vs GDPR and DORA
  • How to Comply with NIS2: A Step-by-Step Plan
  • Frequently Asked Questions
    • Does NIS2 apply to companies outside the EU?
    • Does NIS2 apply to small businesses?
    • What is the NIS2 compliance deadline?
    • What happens if you do not comply with NIS2?
    • Is NIS2 the same as ISO 27001?
  • Conclusion

What Is the NIS2 Directive?

NIS2 — formally Directive (EU) 2022/2555 on measures for a high common level of cybersecurity across the Union — is the EU law that replaced the original NIS Directive of 2016. It entered into force on 16 January 2023, and EU member states were required to transpose it into national law by 17 October 2024. Several states missed that deadline, so national laws have arrived at different times, but the obligations themselves are now a reality across the EU.

The purpose of NIS2 is simple: raise the baseline of cybersecurity across the Union’s most important services, so that a ransomware attack on a hospital, a power grid, a cloud provider or a water utility cannot cascade into a national crisis. It does this in three ways. First, it widens the net: far more sectors and far more organisations are in scope than under NIS1. Second, it prescribes concrete risk-management measures that every in-scope organisation must take. Third, it adds teeth: large fines, strict incident-reporting deadlines, and direct accountability for management bodies.

Unlike a regulation, a directive does not apply directly. Each member state writes its own national law to implement it, which means the exact regulator, registration process and enforcement style vary by country. The core duties, however, are the same everywhere, because they are fixed in the directive itself.

NIS vs NIS2: What Changed?

The original NIS Directive covered only operators of essential services and a small set of digital service providers, and member states chose for themselves which organisations counted. The result was uneven coverage and uneven enforcement. NIS2 fixes that with a size-based rule and a much longer list of sectors.

Area NIS1 (2016) NIS2 (2022)
Sectors covered 7 sectors 18 sectors (11 highly critical, 7 critical)
Who is in scope Chosen by each member state Size-cap rule: medium and large enterprises in covered sectors
Security measures General, high-level duties 10 minimum measures listed in Article 21
Incident reporting Without undue delay 24-hour early warning, 72-hour notification, final report within 1 month
Fines Set nationally, often low Up to €10 million or 2% of global turnover
Management liability Not specified Management must approve measures and can be held liable
Supply chain Barely addressed Explicit supply-chain security duties

Who Must Comply with NIS2?

NIS2 uses a size-cap rule. In general, an organisation is in scope if it is a medium-sized or large enterprise — at least 50 employees, or annual turnover of at least €10 million — and it operates in one of the covered sectors. Some organisations are in scope regardless of size, including providers of public electronic communications networks, trust service providers, top-level domain registries and DNS service providers.

In-scope organisations are divided into two classes: essential entities and important entities. The class determines the level of supervision and the maximum fine.

Essential Entities

Essential entities operate in sectors of high criticality and face the strictest supervision, including proactive checks by regulators. They include energy (electricity, gas, oil, hydrogen, district heating), transport (air, rail, water, road), banking, financial market infrastructures, health (including healthcare providers, laboratories and pharmaceutical manufacturers), drinking water, waste water, digital infrastructure (cloud computing, data centres, content delivery networks, DNS services, domain registries), ICT service management (managed service and managed security service providers), public administration, and space.

Important Entities

Important entities face lighter, reactive supervision — regulators act mainly after an incident or a complaint — but they must meet the same security measures. They include postal and courier services, waste management, manufacture of chemicals, food production and distribution, manufacturing of medical devices, computers and electronics, machinery, motor vehicles and other transport equipment, digital providers such as online marketplaces, online search engines and social networking platforms, and research organisations.

Feature Essential entities Important entities
Sectors Highly critical (Annex I) Other critical (Annex II)
Supervision Proactive, including on-site inspections Reactive, after incidents or evidence of risk
Maximum fine €10 million or 2% of worldwide annual turnover €7 million or 1.4% of worldwide annual turnover
Examples Energy supplier, hospital, cloud provider, bank Food producer, postal service, online marketplace

Two points catch many organisations out. First, NIS2 reaches beyond the EU’s borders in practice: a non-EU company that offers services in the EU, or that supplies an in-scope EU organisation, will be asked to demonstrate NIS2-aligned controls in contracts and security questionnaires. Second, small businesses are mostly out of direct scope, but they are routinely pulled in through supply-chain clauses. For a broader view of how security rules overlap, see our guide to What Is ITAR? International Traffic in Arms Regulations Explained and our overview of the California Consumer Privacy Act (CCPA), which shows how regional rules can shape global compliance programmes.

The 10 Minimum Measures: NIS2 Key Requirements

Article 21 of NIS2 requires in-scope organisations to take appropriate and proportionate technical, operational and organisational measures to manage the risks posed to the security of network and information systems. It lists ten minimum measures that every compliance programme must cover:

# Minimum measure What it means in practice
1 Risk analysis and information security policies Documented risk assessments, a security policy, and regular reviews
2 Incident handling Detection, triage, response and recovery procedures, tested regularly
3 Business continuity and crisis management Backups, disaster recovery, and a tested continuity plan
4 Supply-chain security Security requirements for suppliers and vulnerability checks on their products
5 Security in acquisition, development and maintenance Secure development, patching, and vulnerability handling and disclosure
6 Policies to assess the effectiveness of measures Audits, testing and metrics that prove controls actually work
7 Basic cyber hygiene and cybersecurity training Staff awareness training and everyday hygiene such as patching
8 Cryptography and, where appropriate, encryption Encryption of data in transit and at rest, and proper key management
9 Human resources security, access control and asset management Least privilege, joiner-mover-leaver processes, and an asset inventory
10 Multi-factor authentication and secure communications MFA, and secured voice, video, text and emergency communication systems

The measures must be proportionate to the risk: a large energy operator is expected to do far more than a medium-sized food producer. But “proportionate” is not an excuse for doing nothing — regulators expect documented risk assessments that justify the controls you chose, and evidence that they are working.

disaster recovery plan document with a checklist on a desk

Incident Reporting Under NIS2

NIS2 replaces the vague “without undue delay” duty with a hard timetable. When an in-scope organisation becomes aware of a significant incident, it must report it to its national CSIRT or competent authority in three stages:

  • Early warning within 24 hours: a short report stating whether the incident is suspected to be caused by unlawful or malicious action and whether it could have cross-border impact.
  • Incident notification within 72 hours: a fuller report with an initial assessment of severity, impact and indicators of compromise.
  • Final report within one month: a detailed description of the incident, its severity and impact, the type of threat or root cause, and the mitigation measures applied and planned.

A significant incident is one that has caused, or is capable of causing, severe operational disruption or financial loss, or that has affected — or could affect — other people by causing considerable material or non-material damage. In practice, most ransomware incidents, major outages and data breaches at in-scope organisations are reportable. Organisations should also notify the recipients of their services if the incident is likely to affect them, and they must keep records that allow the regulator to verify the timeline.

The 24-hour clock is the part most organisations underestimate. You cannot meet it without a tested incident response plan, a clear decision-maker, and a pre-agreed route to your national CSIRT. Tabletop exercises that rehearse the first 24 hours are one of the highest-value preparations you can make.

Penalties and Management Liability

NIS2 fines are modelled on the GDPR. Essential entities face administrative fines of up to €10 million or 2% of their total worldwide annual turnover, whichever is higher. Important entities face up to €7 million or 1.4%. Regulators can also order organisations to stop non-compliant practices, and in serious cases can temporarily ban a person from management functions.

The management liability provisions are genuinely new. The management body of an essential or important entity must approve the cybersecurity risk-management measures, oversee their implementation, and can be held liable for infringements. Management bodies must also follow regular training so they can identify risks and assess cybersecurity practices. In short, cybersecurity is no longer something the board can delegate and forget — NIS2 makes it a board-level duty.

NIS2 vs GDPR and DORA

NIS2 is often confused with two other European laws. The differences matter, because many organisations must comply with more than one of them.

Law Protects Applies to Key duty
NIS2 Network and information systems Essential and important entities Risk management and incident reporting
GDPR Personal data Any organisation handling EU personal data Data protection, breach notification in 72 hours
DORA Financial sector resilience Financial entities and their ICT providers Digital operational resilience, testing, third-party risk

A single incident can trigger duties under all three at once — for example, a ransomware attack on a bank that exposes customer data must be reported under NIS2, notified under the GDPR, and managed under DORA. A joined-up incident response plan should cover all three clocks, not just one.

How to Comply with NIS2: A Step-by-Step Plan

  1. Confirm your scope. Map your sectors, size, and the services you provide in each member state. Decide whether you are essential or important, and whether any part of your business is in scope regardless of size.
  2. Register. Find your national competent authority or CSIRT and complete any registration it requires. Some states run a single portal; others split duties by sector.
  3. Run a gap assessment. Measure your current controls against the ten Article 21 measures and the incident-reporting timetable. Use an established framework such as ISO 27001 to structure the work — our guide to data security management explains the core pillars, process and tools involved.
  4. Fix the basics first. Asset inventory, patching, MFA, backups that are tested, and phishing-resistant authentication deliver most of the risk reduction for most organisations.
  5. Write and test the incident plan. Define who decides, who calls the CSIRT, and what evidence you preserve. Rehearse the 24-hour early warning with a tabletop exercise.
  6. Secure the supply chain. Add security requirements to supplier contracts, assess critical suppliers, and plan for the failure of a key vendor.
  7. Train management and staff. Give the board the training NIS2 requires, and give every employee regular cyber hygiene training.
  8. Document and measure. Keep records of risk assessments, decisions, tests and incidents. Regulators will ask for evidence, not intentions.
  9. Review continuously. Reassess risks when services, suppliers or threats change, and report incidents on time — a late report is itself an infringement.

Frequently Asked Questions

Does NIS2 apply to companies outside the EU?

Directly, NIS2 applies to entities established in the EU and to certain providers of services in the EU. In practice, non-EU companies are pulled in through supply-chain requirements: if you sell to an in-scope EU organisation, expect NIS2-aligned security clauses and questionnaires in your contracts.

Does NIS2 apply to small businesses?

Generally no — the size-cap rule excludes micro and small enterprises. Exceptions exist for organisations that are critical regardless of size, such as DNS providers and trust service providers, and small suppliers can still face NIS2 requirements through their customers’ contracts.

What is the NIS2 compliance deadline?

Member states had to transpose NIS2 into national law by 17 October 2024. Several states were late, so the practical deadline is the date your national law took effect. Do not wait for a reminder letter: the duties apply from the national law, and enforcement is already under way in several countries.

What happens if you do not comply with NIS2?

Regulators can impose fines of up to €10 million or 2% of worldwide turnover for essential entities (up to €7 million or 1.4% for important entities), issue binding instructions, and in serious cases suspend certifications or bar individuals from management roles. Non-compliance can also cost contracts, as in-scope customers exclude suppliers that cannot demonstrate NIS2-aligned controls.

Is NIS2 the same as ISO 27001?

No. ISO 27001 is a voluntary international standard for information security management; NIS2 is binding EU law. An ISO 27001-certified management system is, however, an excellent foundation for NIS2 compliance, because it already covers risk assessment, controls, audits and continual improvement.

Conclusion

NIS2 raises the bar for cybersecurity across the European Union: more sectors, clearer measures, faster incident reporting, bigger fines and real management accountability. The organisations that will cope best are the ones that start with an honest scope and gap assessment, fix the fundamentals, test their incident plan, and treat supply-chain security as part of their own security. Start with the ten Article 21 measures, rehearse the 24-hour report, and document everything.

Author

admin

Follow Me
Other Articles
private cloud security
Previous

Cloud Security Best Practices: The Complete Guide for 2026

access control entry list on a security settings screen
Next

WPA2 Password: How It Works, Length Rules and How to Make It Strong

One Comment
  1. RTO and RPO Explained: Difference, Examples & How to Set Them says:
    November 10, 2026 at 3:23 am

    […] tested. For organisations in scope, recovery capability also matters for compliance — see the NIS2 Directive, which expects in-scope entities to handle incidents and restore […]

    Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • Compliance Risk Assessment: A Complete Guide for 2026
  • SX SFP Module: What It Is, How It Works, and When to Use It
  • Hotspot 2.0 (Wi-Fi Passpoint): What It Is and How It Works
  • Volume Boot Record (VBR): What It Is, How It Works, and How to Fix It
  • Can Website Owners See Who Visits Their Website? What They Can (and Cannot) See

Recent Comments

  1. Compliance Risk Assessment: A Complete Guide for 2026 on ISO 27001 Compliance: What It Is, How to Get Certified, and How to Stay Compliant
  2. SX SFP Module: What It Is, How It Works & When to Use It on Network Access Control: What It Is, How It Works, Types and Examples
  3. Hotspot 2.0 (Wi-Fi Passpoint): What It Is & How It Works on WIPS: What Is a Wireless Intrusion Prevention System?
  4. Volume Boot Record (VBR): What It Is & How to Fix It on Hypervisor: What It Is, Types, Security Risks and How to Harden It
  5. Can Website Owners See Who Visits? What They See & Can't See on California Consumer Privacy Act (CCPA): What It Is, Your Rights, and How to Comply in 2026

Archives

  • November 2026
  • October 2026
  • September 2026
  • August 2026
  • July 2026
  • June 2026
  • May 2026
  • February 2026

Categories

  • Blog
  • Business
  • Security Tips
  • Tech
  • Travel
  • Uncategorized
Copyright 2026 — Cloud Security Tips. All rights reserved. Blogsy WordPress Theme

Powered by CookieAdmin
Necessary cookies enable essential site features like secure log-ins and consent preference adjustments. They do not store personal data.
None
Functional cookies support features like content sharing on social media, collecting feedback, and enabling third-party tools.
None
Analytical cookies track visitor interactions, providing insights on metrics like visitor count, bounce rate, and traffic sources.
None
Advertisement cookies deliver personalized ads based on your previous visits and analyze the effectiveness of ad campaigns.
None
Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies.
None
Powered by CookieAdmin