NIS2

NIS2 Directive: Five Key Things to Watch

The NIS2 Directive came into force across the EU on 17 October 2024. Here are the five most important changes you need to know about.

  1. 18
    sectors covered, up from 7 in previous legislation
    NIS2 Directive
  2. 24
    hours for initial incident reporting
    NIS2 Directive Article 23
  3. €10
    €10 million maximum fines for essential entities
    NIS2 Directive Article 34

NIS2 is Here

On 17 October 2024, the EU entered a new era of cybersecurity. The NIS2 Directive — the enhanced Network and Information Security legislation — became mandatory across all Member States. For organizations within scope, this means new obligations, stricter requirements, and potentially significant sanctions.

But this isn’t just about avoiding fines. When properly implemented, NIS2 becomes a catalyst for genuinely strengthening your organization’s digital resilience.

Important to understand: NIS2 is not a one-time project. It’s a continuous process that requires security to become an integrated part of operations — from the boardroom to the server room.

The Five Most Important Changes

Here are the five areas that will affect most organizations:

1. More sectors covered

The number of sectors covered has more than doubled — from 7 to 18. Manufacturing, food, waste management, and research organizations are just some of the new sectors. If you previously avoided regulation, things may be different now.

2. Management becomes personally liable

Cybersecurity is no longer just the IT department's responsibility. Boards and management must approve security policies, ensure resources, and undergo training. This responsibility cannot be delegated away.

3. 24-hour reporting

For significant security incidents, an early warning must be sent within 24 hours — not 72 as previously. This requires prepared processes and incident response plans that work even at three in the morning.

4. Dramatically increased sanctions

Maximum fines have increased dramatically. Essential entities risk up to €10 million or 2% of global turnover. These are levels previously only seen with GDPR.

5. Entire supply chain scrutinized

NIS2 places explicit requirements on supply chain security. This means organizations must:

  • Assess security risks with suppliers
  • Set security requirements in contracts
  • Monitor and verify compliance
  • Have contingency plans for incidents at sub-suppliers

Consequence: Even if you’re not directly covered by NIS2, you may be affected indirectly through requirements from your customers.

Who is Covered?

Size Criteria

Generally, organizations that meet at least one of the following are covered:

  • At least 50 employees
  • At least €10 million in annual turnover

Essential Entities (strictest requirements)

  • Energy (electricity, oil, gas, district heating, hydrogen)
  • Transport (aviation, rail, road, maritime)
  • Banking and financial market infrastructure
  • Healthcare
  • Drinking water and wastewater
  • Digital infrastructure (DNS, data centers, cloud)
  • ICT service management (B2B)
  • Public administration (central level)
  • Space (ground-based infrastructure)

Important Entities

  • Postal and courier services
  • Waste management
  • Chemicals
  • Food
  • Manufacturing (medical devices, electronics, automotive, machinery)
  • Digital services (marketplaces, search engines, social platforms)
  • Research

Unsure if you’re covered? Try our NIS2 classification tool to get an answer in minutes.

What Do the New Requirements Mean in Practice?

  1. Risk management Implement systematic risk management for network and information systems. This includes risk assessments, security policies, and technical measures tailored to the risks.
  2. Incident handling Establish processes to detect, handle, and report security incidents. Have clear roles, contact paths, and escalation procedures documented and practiced.
  3. Business continuity Ensure operations can continue during disruptions. This covers backup, disaster recovery, and crisis plans that are tested regularly.
  4. Supplier security Assess and manage security risks in the supply chain. Set requirements for suppliers and follow up to ensure requirements are met.
  5. Training and awareness Ensure staff have the knowledge needed. This particularly applies to management, who must undergo specific cybersecurity training.

Timeline: What Applies Now?

DateEvent
17 Oct 2024NIS2 Directive came into force
VariousMember State implementation deadlines
OngoingSupervision and controls commence
Upon incident24 hours for early warning

Common Mistakes to Avoid

Wait and see

The directive is already in force. Waiting risks both sanctions and security incidents. Start now — even small steps in the right direction are valuable.

See it as an IT project

Cybersecurity is a business issue, not a technology issue. Without management engagement and whole organization participation, efforts will be half-hearted.

Buy a "solution"

There are no shortcuts. Tools help, but they don't replace processes, culture, and competence. Choose tools that support your way of working.

Forget the suppliers

Your security is no stronger than the weakest link in the chain. Map your critical suppliers and begin dialogue about security requirements.

For a deeper review of the NIS2 Directive’s structure and all requirement areas, see our complete NIS2 framework overview.

How Securapilot Can Help

Securapilot is built to support organizations through the entire NIS2 compliance journey:

  • GAP analysis — Map where you stand today against requirements
  • Risk management — ISO 27005-based risk assessment and treatment
  • Incident handling — Documentation and report generation within time requirements
  • Supplier management — Assessment and monitoring of suppliers
  • Management dashboard — Overview for board and management

Book a demo and see how we can help your organization.


Frequently asked questions

When did the NIS2 Directive come into force?

The NIS2 Directive came into force on 17 October 2024. Organizations covered by the directive should have already begun their compliance work.

What is the difference between NIS2 and national implementations?

NIS2 is the EU directive that sets minimum requirements. Each Member State implements the directive through national legislation. In practice, the requirements are very similar, but national laws may adapt certain aspects to local conditions.

Which authorities oversee NIS2 compliance?

ENISA provides oversight at the EU level, but each Member State has designated national competent authorities for supervision within their respective sectors, such as financial regulators for the banking sector.

Can board members be held personally liable?

Yes, NIS2 explicitly requires management accountability. In cases of serious breaches, management personnel can be held liable and in extreme cases may be prohibited from holding management roles.


#NIS2#cybersecurity#compliance#EU#legislation

We use anonymous statistics without cookies to improve the website. Read more