European Unionregulation

NIS2 Directive

NIS2 introduces direct accountability for management bodies who fail to oversee cybersecurity risk across 18 critical sectors.

Mapped to Microsoft controls
Effective Date18 October 2024 (transposition deadline)
Enforcement BodyNational competent authorities in each EU member state
Penalty FrameworkEssential entities face administrative fines of up to EUR 10 million or 2% of total annual worldwide turnover (whichever is higher). Important entities face fines of up to EUR 7 million or 1.4% of turnover. Member states can impose additional measures including temporary suspension of certifications, temporary prohibition of management functions, and orders to bring practices into compliance. Management body members can be held personally liable for failures to approve and oversee cybersecurity risk management measures.

The NIS2 Directive (EU) 2022/2555 establishes the baseline for critical infrastructure cybersecurity across the EU. It designates 'essential' and 'important' entities across sectors like energy, finance, healthcare, and digital infrastructure.

The directive mandates extreme risk management protocols, strict 24-hour incident reporting, deep supply chain security assessments, and explicit management accountability. Board members can face personal legal repercussions for systemic compliance failures.

To meet NIS2 obligations, we deploy a hardened operational layer inside your M365 environment. This includes establishing Zero-Trust identity boundaries, configuring Microsoft Sentinel for rapid threat classification, and generating the structured incident evidence necessary to satisfy competent authorities and protect executive liability.

Why This Matters Now

NIS2 has aggressively expanded EU cybersecurity obligations across 18 critical sectors. With enforcement active since October 2024, entities must report significant incidents within 24 hours and maintain enterprise-grade cybersecurity measures. Crucially, NIS2 introduces direct accountability for management bodies who fail to oversee these risks. For M365-dependent enterprises, NIS2 demands deterministic technical controls for Zero-Trust identity management, advanced encryption, rapid incident detection, and verifiable business continuity.

Scope & Applicability

NIS2 applies to two categories: Essential entities (energy, transport, banking, financial market infrastructure, health, drinking water, wastewater, digital infrastructure, ICT service management, public administration, space) and Important entities (postal services, waste management, chemicals, food, manufacturing of medical devices/computers/electronics/machinery/motor vehicles, digital providers including cloud, search engines, online marketplaces, social networks). Medium-sized enterprises (50+ employees or EUR 10M+ turnover) in these sectors are automatically in scope. Some entities are in scope regardless of size.

Core Obligations

01
Article 21

Risk Management Measures

Implement appropriate and proportionate technical, operational, and organisational measures to manage risks to network and information systems. This includes incident handling, business continuity, supply chain security, and vulnerability handling.

02
Article 23

Incident Reporting

Submit an early warning within 24 hours, an incident notification within 72 hours, and a final report within one month of a significant incident.

03
Article 21(2)(d)

Supply Chain Security

Address cybersecurity risks in the supply chain, including security-related aspects concerning relationships with direct suppliers and service providers.

04
Article 20

Management Accountability

Management bodies must approve and oversee cybersecurity risk management measures, undergo training, and can be held personally liable for infringements.

05
Article 21(2)(c)

Business Continuity

Ensure business continuity including backup management, disaster recovery, and crisis management procedures.

Microsoft 365 Control Mapping

How each obligation maps to enforceable Microsoft 365 controls and the evidence they produce.

Obligation

Article 23 - 24-Hour Incident Reporting

M365 Control

Sentinel rigorous incident classification with NIS2 significance criteria. Rapid early warning draft generation within 4 hours of detection. Evidence chain preservation in immutable storage.

Evidence

Verified incident detection-to-classification timeline, early warning generation logs, robust evidence integrity chain.

Obligation

Article 21 - Risk Management

M365 Control

Microsoft Secure Score as continuous risk metric. Conditional Access enforcing risk-based authentication. Defender Vulnerability Management for continuous asset assessment.

Evidence

Monthly Secure Score trend reports, risk-based CA evaluation logs, vulnerability management posture reports.

Obligation

Article 21(2)(d) - Supply Chain Security

M365 Control

Defender for Cloud Apps monitoring all third-party integrations. OAuth app consent workflow requiring admin approval. Service principal permission reviews quarterly.

Evidence

Third-party app inventory, OAuth consent policy configuration, service principal audit reports.

Obligation

Article 21(2)(c) - Business Continuity

M365 Control

Microsoft 365 backup via Backup Storage. SharePoint and OneDrive retention policies with point-in-time recovery. Exchange Online archive with litigation hold for critical mailboxes.

Evidence

Backup configuration report, recovery point objective (RPO) metrics, restore test results.

Implementation Timeline

December 2022
NIS2 Directive (EU 2022/2555) published in the Official Journal
January 2023
NIS2 enters into force
October 2024
Member state transposition deadline
October 2024
Organisations must comply with national implementing legislation
April 2025
Member states must establish lists of essential and important entities

Related Frameworks

Ready to get NIS2-ready?

Start with a fixed-scope sprint. We assess your Microsoft 365 controls against NIS2 requirements, close gaps, and produce audit-ready evidence.