Regulation

NIS2 and the case
for airgap solutions

The NIS2 Directive is the EU's most significant cybersecurity legislation to date. It mandates specific technical security measures for thousands of organisations across Europe — and airgap solutions are one of the most direct ways to implement them.

In forceOctober 2024
ScopeEU-wide, all member states
Key articleArticle 21 — security measures
Max fine€10M or 2% global turnover
Background

What is the NIS2 Directive?

NIS2 (Directive EU 2022/2555) replaces the original NIS Directive from 2016. It significantly expands the scope of mandatory cybersecurity obligations across the EU — covering more sectors, more organisations, and imposing stricter requirements and higher penalties. Member states were required to transpose NIS2 into national law by October 2024.

The original NIS Directive covered only operators of essential services and digital service providers. NIS2 doubles down: it creates two categories — essential entities and important entities — and applies mandatory cybersecurity requirements to both. The distinction affects supervisory intensity and fines, not the technical requirements themselves.

Crucially, NIS2 shifts liability explicitly to senior management. Board members and executives can now be held personally responsible for cybersecurity failures, including failure to implement adequate technical measures.

Essential entities

EnergyElectricity, oil, gas, district heating, hydrogen
TransportAir, rail, water, road
Banking & financial market infrastructure
HealthHospitals, labs, pharmaceutical manufacturers
Drinking water & wastewater
Digital infrastructureDNS, IXPs, cloud, datacenters, CDNs
ICT service management (B2B)
Public administration
Space

Important entities

Postal & courier services
Waste management
ChemicalsProduction and distribution
FoodProduction, processing and distribution
ManufacturingMedical devices, electronics, machinery, vehicles
Digital providersOnline marketplaces, search engines, social platforms
Research organisations

Size thresholds apply: generally medium-sized (50+ employees, €10M+ turnover) and large organisations. Some sectors have no size threshold.

The core obligation

Article 21 — what organisations must implement

Article 21 is the technical heart of NIS2. It requires organisations to implement "appropriate and proportionate technical, operational and organisational measures" based on a risk assessment. The article lists ten minimum measures. Several of these directly map to what an airgap solution provides.

Art. 21(2)(a)

Risk analysis & information system security policies

Organisations must have documented policies covering how risks are identified and managed across their network and information systems.

An airgap deployment is direct evidence of a risk-based decision to physically isolate high-value systems from attack vectors. It documents an architecture choice, not just a policy.
Art. 21(2)(c)

Business continuity & backup management

Backup management, disaster recovery, and crisis management must be in place. Backups must be protected from the threats that affect the primary systems.

A data diode protecting a backup vault (e.g. Veeam offsite replication) makes backups physically unreachable from ransomware — directly satisfying this requirement.
Art. 21(2)(d)

Supply chain security

Organisations must address security risks in supply chains, including the security posture of suppliers and service providers with access to their systems.

A data diode at the boundary between a supplier connection and internal OT systems eliminates the risk of lateral movement through the supply chain — a key NIS2 concern.
Art. 21(2)(e)

Security in network and information systems acquisition, development and maintenance

Security must be built into the acquisition and maintenance of systems, including vulnerability handling and disclosure.

Hardware-enforced separation means there is no software configuration to misconfigure, patch incorrectly, or exploit. The security property is physical, not policy-dependent.
Art. 21(2)(b)

Incident handling

Prevention, detection and response to incidents. Organisations must be able to detect, report and recover from security incidents.

A data diode enables safe one-way forwarding of logs and monitoring data from isolated OT or secure networks to a SIEM without creating a return attack path into those environments.

Art. 21(2)(f)

Policies and procedures for assessing effectiveness

Organisations must measure and assess whether their security measures are actually working.

A hardware data diode provides a provable, binary security property — either data flows one way or it doesn't. It is significantly easier to demonstrate effectiveness than software-based controls.

Art. 21(2)(g)

Basic cyber hygiene practices and training

NIS2 explicitly requires organisations to address the human element — training, awareness and baseline hygiene practices.

Art. 21(2)(h)

Cryptography and encryption

Where appropriate, policies on the use of cryptography and encryption must be in place.

Art. 21(2)(i)

Human resources security, access control and asset management

Access control policies, personnel security, and asset management must be in place.

Art. 21(2)(j)

Multi-factor authentication and secure communications

MFA and encrypted communications must be used where appropriate, including for administrative access to systems.

Compliance mapping

How airgap solutions address NIS2 requirements

The table below maps specific airgap deployment patterns to the NIS2 Article 21 requirements they address.

Deployment NIS2 requirement How it addresses it
OT / IT network separation with data diode Art. 21(2)(a) — Risk & policy
Art. 21(2)(d) — Supply chain
Physically prevents lateral movement from IT into OT. Attack surface reduction is demonstrable and hardware-enforced, not reliant on firewall rule correctness. ✓ Direct control
One-way log forwarding from OT to SIEM Art. 21(2)(b) — Incident handling Enables continuous monitoring and incident detection from isolated networks without creating a return attack path. Security teams gain visibility without compromising the protected zone. ✓ Direct control
Airgapped backup vault (Veeam + data diode) Art. 21(2)(c) — Business continuity & backup Backups are replicated to an isolated vault that ransomware physically cannot reach. Restore points are preserved even if the production environment is fully compromised. ✓ Direct control
Supplier / remote access isolation Art. 21(2)(d) — Supply chain security Supplier data feeds (sensor data, telemetry, patches) can be received one-way without giving suppliers any access back into the internal network. Eliminates the supply chain as a lateral movement vector. ✓ Direct control
Camera / physical security network isolation Art. 21(2)(a) — Risk policy
Art. 21(2)(i) — Access control
Isolates IoT-heavy camera networks from corporate and operational systems. A compromised camera cannot pivot to the NVR server or to broader IT infrastructure. ✓ Direct control
CDR (OPSWAT MetaDefender) on data import Art. 21(2)(e) — Secure acquisition
Art. 21(2)(d) — Supply chain
All files crossing the boundary are sanitised via Deep CDR before delivery — every file is treated as potentially malicious regardless of source. Removes malware, macro exploits and embedded threats at the transfer point. ✓ Direct control
Enforcement

Penalties for non-compliance

NIS2 sets minimum fine levels that member states must apply. National implementations may be stricter. Unlike the original NIS Directive, penalties are now explicitly proportionate to the severity of the failure — and management liability is personal.

Essential entities
€10M or 2%

Whichever is higher: €10 million or 2% of total global annual turnover. Applies to the highest-risk sectors — energy, transport, health, water, digital infrastructure, banking.

Important entities
€7M or 1.4%

Whichever is higher: €7 million or 1.4% of total global annual turnover. Applies to manufacturing, food, chemicals, postal services, digital providers and others.

Additionally, member state supervisory authorities can issue binding instructions, order temporary suspension of services, and publicly name non-compliant organisations. Senior management can be held personally liable and barred from management roles.

Getting started

Practical steps toward NIS2 compliance with airgap solutions

NIS2 compliance is not a single product purchase — it is an ongoing programme. But a data diode deployment can address multiple requirements in a single project, with a provable, auditable result.

Step 1

Determine if you are in scope

Check whether your sector and size place you in scope as an essential or important entity. When in doubt, assume you are — national authorities are actively mapping organisations.

Step 2

Map your network boundaries

Identify where IT and OT networks touch. Identify backup systems, supplier connections, remote access points and monitoring feeds. These are your highest-risk boundaries.

Step 3

Prioritise the highest-impact control

A data diode at the OT/IT boundary — plus a protected backup vault — simultaneously addresses Art. 21(a), (c) and (d). That is a strong baseline before touching any other measure.

Step 4

Document the architecture decision

NIS2 requires evidence that measures are in place and effective. Your data diode deployment — with architecture documentation, test reports and supplier certifications — is directly auditable.

Ready to assess your NIS2 exposure?

We help you map your network, identify the right airgap architecture, and produce the documentation that auditors require.

Talk to us Our consultancy process