Try our new Proactive Endpoint Operations Platform and get 25% off at launch!

Read more

IT Security

NIS2 in the EU: Who is affected and what obligations apply

November 03, 2026, Franz Braun

NIS2 is an EU directive. The specific obligations, competent authorities, and deadlines result from the national implementation in each member state. For many organizations and public administrations, this means knowing their systems and risks, managing security incidents, meeting obligations toward the respective national authority, and demonstrably documenting compliance with NIS2 requirements.

NIS2 – At a glance

  • NIS2 is EU Directive (EU) 2022/2555. Most EU member states have now transposed it into national law; however, deadlines and procedures differ.
  • Typically affected are medium-sized and large entities in critical and important sectors. Across the EU, NIS2 distinguishes between essential entities and important entities.
  • The NIS2 requirements comprise three core obligations: registration with the respective competent national authority, reporting significant security incidents to the competent authority or CSIRT, and documented risk management for which management is responsible.
  • For IT, demonstrability is what matters most: inventory, patch status, incident documentation, and the supply chain must be verifiable; otherwise, implementation exists only on paper.

A sales employee loses their personal smartphone with a CRM app installed and access to customer data. IT may be able to lock the device, but it must also determine what cybersecurity damage may have occurred. This is precisely where NIS2 becomes operationally relevant. Under the NIS2 directive, IT security is no longer solely the responsibility of the IT department. Entire organizations or public administrations and their management now bear documented responsibility.

What is NIS2 and when does it apply in the EU?

NIS2 is EU Directive (EU) 2022/2555 (opens in new tab) and establishes a harmonized legal framework for the security of network and information systems. The EU defines the binding framework; however, each member state defines the national law, competent authority, registration procedure, and deadlines.

Organizations should therefore check the current national deadlines for registration, incident reporting obligations, and risk management.

Who must implement NIS2 and who is affected?

NIS2 generally covers medium-sized and large entities in critical and important sectors. Whether an organization is affected depends on the sector, type of entity, and often the size of the organization (opens in new tab).

Affected sectors include, among others, energy, transport, health, finance, water management, digital infrastructure, public electronic communications, waste and wastewater management, postal and courier services, public administration, and the space sector.

How to make an initial assessment of who is affected by NIS2:

  1. Check whether the organization belongs to a NIS2 sector.
  2. Clarify whether it is classified as an essential or important entity.
  3. Compare headcount, revenue, and balance sheet total with the statutory thresholds.
  4. Check special cases with data protection, legal, or compliance officers.

The assessment is not a one-time exercise: growth, new services, or a changed role in the supply chain can alter the classification. What matters are the sector, type of entity, size thresholds, and definitions in the national implementation law.

Which NIS2 requirements and obligations apply?

Covered entities must fulfill three core obligations:

  • Registration: Affected organizations register with the respective competent national authority.
  • Incident reporting obligation: Significant security incidents must be reported to the competent authority or CSIRT.
  • Risk management: Appropriate measures must be implemented and documented.

These include, for example, risk analyses, incident handling, business continuity, training, vulnerability management, and securing the supply chain.

The NIS2 directive also places responsibility on top management. Cybersecurity is therefore not a delegable, purely technical task: management must take responsibility for frameworks, resources, and evidence.

What does NIS2 mean for IT?

For IT teams, NIS2 primarily means attesting compliance. They must be able to prove which devices, systems, applications, and access points exist, which software versions are installed, which vulnerabilities are known, and which measures were taken and when.

NIS2 requirementIT measureProof
Risk managementInventory, vulnerability assessment, prioritizationAsset and vulnerability report, risk register
Incident handlingDetect, assess, contain, escalate, documentIncident record, escalation chain, reporting documentation
Patch and vulnerability managementPlan, test, distribute, and verify updatesPatch status, exceptions, deadlines
Supply chain securityAssess suppliers and software dependenciesSupplier list, security requirements, audit records
Training and awarenessRaise employee awareness of phishing, access, and reporting channelsTraining records, awareness measures
Table: Overview of NIS2 requirements, IT measures and evidence

Incident response (opens in new tab) in the context of NIS2 means detecting, assessing, containing, escalating, and documenting security incidents in a defined process. Many national implementations require an early warning within 24 hours as well as further follow-up reports. The deadlines and procedures of the respective competent national authority always take precedence. Not every technical incident is “significant”; only one that has caused or may cause a severe operational disruption or significant damage qualifies.

No single tool guarantees NIS2 compliance

Registration, incident reporting obligations, and risk management require an interplay of processes, responsibilities, and multiple IT solutions, for example for monitoring, identity and access management, backup, network security, and others.

A unified endpoint management solution such as the baramundi Management Suite (opens in new tab) can contribute important technical building blocks: It provides transparency over endpoints and software and supports inventory, patch management, software distribution, and MDM, as well as encryption and access control. It therefore addresses a relevant portion of the NIS2 requirements, but it does not replace monitoring, IAM, backup, or network security, nor the organizational processes behind them.

What remains decisive is operations: An inventory without maintenance, a patch process without exception management, or an incident plan without a tested reporting chain fulfills the NIS2 requirements only on paper.

Even more detailed information: Implementing NIS2 on a technical level

How can inventory, vulnerability management, patching, encryption, and access control be efficiently organized in an existing IT landscape? The white paper “NIS2 Directive: Cybersecurity in the EU” maps the relevant NIS2 requirements and shows how the baramundi Management Suite can support them.

Conclusion: Know the limits and conflicting objectives of NIS2

In summary: NIS2 does not create security merely through compliance. A registered organization remains vulnerable if endpoints are not patched, access is not controlled, or employees do not report security incidents.

However, measures must not unnecessarily complicate day-to-day work: An overly restrictive device policy promotes shadow IT (opens in new tab), while too many exceptions weaken demonstrability and protection. Balance is achieved through risk-based rules, clear responsibilities, and regular review. Those who implement the NIS2 requirements in an operationally effective way not only meet NIS2 formally but also strengthen the resilience of business operations.

Important: Changes may still occur in the future. In January 2026, the European Commission already proposed targeted amendments to the NIS2 directive to improve legal clarity and implementability. Organizations should monitor this development.

Categories: IT Security