TroutTrout
NIS2 compliance for OT and industrial sites

Apply NIS2 Article 21 down to the machines on your shop floor.

NIS2 requires industrial operators to apply the ten Article 21 measures to their OT. They report significant incidents within 24 hours. Access Gate controls and logs every access to your machines, on premise.

Last updated:

SITE PLAN · NIS2 ZONESEU DIRECTIVE 2022/2555ZONE A · OTPROCESSSCADAPRODUCTIONTURBINEFIELD DEVICESPLCRTUHMIDCSSAFETY SYSSUBSTATIONTAGZONE B · ITADMINERP · EMAILSERVERSDATA CTRNETWORKVPNWIFIMGMTVENDOR ACCESSOT PERIMETERIT PERIMETERARTICLE 21RISKINCIDENTACCESSENCRYPTSUPPLYCONTINUITY
Valve wheels on vertical pipes in a plant

The problem

Article 21 applies to every asset in scope, including PLCs, HMIs, CNC machines, SCADA servers and sensors on the production floor. Many of them run proprietary firmware or an end-of-life operating system and cannot take an endpoint agent. The directive has no exemption for these machines.

NIS2 requirements for OT

What does NIS2 require for OT and industrial control systems?

NIS2 makes no distinction between IT and OT. An industrial operator in scope manages cyber risk with the ten measures of Article 21. It reports significant incidents under Article 23. Under Article 20, its management approves and oversees the measures. The directive counts PLCs, HMIs, SCADA servers and engineering workstations as network and information systems, and the obligations apply to them.

Who is in scope

NIS2 covers the 11 sectors of Annex I (energy, transport, banking, financial market infrastructures, health, drinking water, waste water, digital infrastructure, ICT service management, public administration and space) and the 7 sectors of Annex II (postal and courier services, waste management, chemicals, food, manufacturing, digital providers and research). Manufacturing in Annex II covers medical devices, computer, electronic and optical products, electrical equipment, machinery and equipment, motor vehicles and other transport equipment.

The size rule brings in medium and large enterprises: 50 or more employees, or more than €10M in both annual turnover and balance sheet total. Some entities are in scope whatever their size, such as providers of public electronic communications, trust service providers, DNS service providers and an entity that is the sole provider in its Member State of a service essential to society.

Large enterprises in Annex I sectors are essential entities. Most other entities in scope are important entities. Both apply the same measures. Essential entities face proactive supervision and higher fines.

The ten measures of Article 21(2)

Article 21(2) lists the minimum measures each entity in scope applies, in proportion to its risk.

  • (a) Policies on risk analysis and information system security
  • (b) Incident handling
  • (c) Business continuity, such as backup management and disaster recovery, and crisis management
  • (d) Supply chain security, including the relationships with direct suppliers and service providers
  • (e) Security in network and information systems acquisition, development and maintenance, including vulnerability handling and disclosure
  • (f) Policies and procedures to assess the effectiveness of cybersecurity risk-management measures
  • (g) Basic cyber hygiene practices and cybersecurity training
  • (h) Policies and procedures on the use of cryptography and, where appropriate, encryption
  • (i) Human resources security, access control policies and asset management
  • (j) Multi-factor or continuous authentication, secured voice, video and text communications and secured emergency communications, where appropriate
01

Incident reporting under Article 23

An entity reports each significant incident to its CSIRT or competent authority in three steps. It sends an early warning within 24 hours of becoming aware of it, an incident notification within 72 hours, and a final report no later than one month after the notification. Access Gate session logs record who reached which machine, and when. Your team takes the facts for each report from them.

02

Management accountability under Article 20

The management body approves the Article 21 measures, oversees their implementation and can be held liable for breaches. Its members must follow cybersecurity training. See NIS2 management liability.

03

Fines under Article 34

The directive requires Member States to provide maximum fines of at least €10M or 2% of total worldwide annual turnover in the preceding financial year for essential entities. For important entities, the floor is €7M or 1.4%. In both cases the higher amount applies. Source: Directive (EU) 2022/2555, Article 34.

The parts of Article 21 Access Gate enforces at the network

These parts of Article 21 depend on who and what can reach your machines. Access Gate enforces the network part on site.

  • Supply chain security (d). Suppliers and integrators reach only the machines you allow, for a limited time and with MFA, and every session is recorded. See secure remote access for OT.
  • Access control and MFA (i, j). Each user signs in with MFA at Access Gate before a session reaches a PLC or HMI. The machine itself never has to support MFA.
  • Asset management (i). The asset inventory lists every machine from the traffic already on your network. Nothing is installed on the machines.
  • Zones between OT and IT (a, g, i). Access Gate splits OT into zones and blocks every connection you have not allowed, following the zones and conduits model of IEC 62443. Recital 89 lists network segmentation among cyber hygiene practices.
  • Logging for incident handling (b). Every connection is logged with user, machine and time. Your team uses this log for the 24-hour early warning.

What stays with you

Access Gate does not make an entity compliant on its own. Your team writes the risk analysis and the security policies, handles and reports incidents, plans business continuity, patches systems, sets security terms in supplier contracts and trains staff. Access Gate provides the enforcement and the evidence for the network part of the measures.

Key figures

Three NIS2 figures and their sources.

Each figure links to the primary text.

24 h, 72 h, 1 month
Early warning, incident notification and final report after a significant incident.
Directive (EU) 2022/2555, Article 23(4)
18 sectors
11 highly critical sectors in Annex I and 7 other critical sectors in Annex II.
Directive (EU) 2022/2555, Annexes I and II
15 or 20 objectives
Security objectives in France's ReCyF, published by ANSSI on 17 March 2026. Important entities have 15. Essential entities have all 20.
ANSSI, Référentiel Cyber France (ReCyF)
National transposition

How France and Germany transpose NIS2

NIS2 is a directive, so each Member State writes it into national law and names its own authority. The transposition deadline was 17 October 2024.

France: ANSSI and the projet de loi Résilience

France transposes NIS2 through the bill on the resilience of critical infrastructure and the strengthening of cybersecurity, known as the projet de loi Résilience. The Senate adopted it in March 2025. Its examination by the National Assembly, planned for October 2026, was withdrawn from the agenda. The bill is back on the agenda from 9 November 2026. ANSSI is the national authority. It states that NIS2 obligations will apply in France once the law is promulgated and its implementing decrees are published. ANSSI tracks progress on its transposition status page. Pending those texts, its ReCyF sets out 15 security objectives for important entities and 20 for essential entities.

Germany: NIS2UmsuCG and BSI registration

Germany transposed NIS2 with the NIS2 Implementation and Cybersecurity Strengthening Act (NIS2UmsuCG), which rewrites the BSI Act (BSIG). The act was promulgated on 5 December 2025 and has applied since 6 December 2025. The BSI supervises about 29,500 entities, classed as particularly important or important. Each entity registers with the BSI within three months of falling in scope. Registration starts in Mein Unternehmenskonto and continues in the BSI portal. Section 30(2) BSIG lists the ten minimum measures.

How Access Gate applies Article 21 to machines that cannot run agents.

Access Gate applies the measures at the network, in front of the machines. You connect it to your existing firewall or router and add one rule that forwards the machine traffic to it. Nothing is installed on the machines, and their firmware stays as it is.

Operators with several plants deploy one Access Gate per plant, with no dependency between plants. Each plant gets its own IEC 62443 zones, and you manage the policies of every plant from one place.

01

Segmentation without re-cabling

Access Gate separates OT zones from IT and from each other. Your VLANs and switches stay as they are.

02

MFA in front of each machine

Access Gate checks MFA before a session reaches the machine, so the PLC never has to support it. This answers the access control and MFA measures in points (i) and (j).

03

A hash-chained log of every OT session

Every connection to an OT asset is logged with user, time and protocol, and sessions can be replayed. The log is hash-chained, so any alteration is detectable.

OT segmentation

Does NIS2 require OT segmentation?

Yes, in practice. Article 21(2) of the directive does not use the word. It requires policies on risk analysis and information system security (point a), basic cyber hygiene (point g) and access control (point i). Recital 89 lists network segmentation among cyber hygiene practices.

The implementing rules are explicit. Point 6.8 of the annex to Implementing Regulation (EU) 2024/2690 requires digital-sector entities to split systems into zones and keep safety-critical systems in secured zones. ENISA's technical implementation guidance (June 2025) explains how to apply it and test it.

French national rules require segmentation too. Objective 7 of the ReCyF published by ANSSI requires essential entities to split their systems into security zones and control the traffic between them. The rule covers traffic from providers and suppliers as well.

Access Gate segments OT without re-cabling. You connect it to your existing firewall or router and add one rule. It applies zone policies at the network, and nothing is installed on the machines.

Access Gate installs beside your network.

Connect it to your existing firewall or router and add one rule. There is no re-cabling.

Access Gate sets access policies between OT and IT.

Decide how servers, PLCs and HMIs connect to corporate systems. Policies apply at the network, and nothing is installed on the machines.

OT ZONESCADATAGIT ZONEERPVPNMESINCIDENT LOG

Each Article 21 measure gets its own evidence.

Access logs and policy reports are ready when the auditor asks for them.

NIS2 ARTICLE 21Risk Management (a)PARTIncident Handling (b)PARTBusiness Continuity (c)PARTSupply Chain (d)FULLNetwork Security (e)PARTAccess Control (i)FULL
Article 21(2) mapping

How Access Gate maps to each Article 21(2) measure.

For each of the ten measures, here is what the directive requires, what Access Gate does at the network and what stays with you. Enforced means Access Gate applies the technical control. Supports means it covers part of the measure or provides evidence for it.

Article 21(2) at a glance: each measure and the Access Gate control that answers it.
ArticleMeasureAccess Gate controlCoverage
Art. 21(2)(a)Risk analysis and information system security policiesAsset inventory and deny-by-default rules feed your risk analysis. Writing the policy stays with you.Supports
Art. 21(2)(b)Incident handlingSession logs, alerts and replay for the 24-hour early warning. Notifying the authority stays with you.Supports
Art. 21(2)(c)Business continuity and crisis managementAccess Gate connects beside the network, so production keeps running if it stops. Disaster recovery stays with you.Supports
Art. 21(2)(d)Supply chain securityEach vendor session uses MFA, is recorded and is revoked automatically. Supplier contracts stay with you.Enforced
Art. 21(2)(e)Security in system acquisition, development and maintenanceAccess Gate discovers unmanaged machines passively and applies deny-by-default rules around unpatched ones. Vulnerability handling stays with you.Supports
Art. 21(2)(f)Effectiveness assessmentYou can audit access policies and export evidence packages on demand.Supports
Art. 21(2)(g)Cybersecurity hygiene and trainingPolicy enforces MFA, least privilege and session timeouts. Staff training stays with you.Supports
Art. 21(2)(h)Cryptography and encryptionEvery access path is encrypted with TLS. The policy stays with you.Enforced
Art. 21(2)(i)Access control and asset managementPassive asset inventory and identity-based access per user, machine and protocol. Human resources security stays with you.Enforced
Art. 21(2)(j)Multi-factor authenticationMFA at the gate before any session reaches the machine, with offline TOTP. Secured voice and video stay with you.Enforced
Art. 21(2)(a)Risk analysis and information system security policies Supports
What NIS2 requires

Establish and maintain risk management policies for all information systems.

How Access Gate addresses it

Access Gate provides continuous asset discovery, network mapping, and policy enforcement. Risk is managed through microsegmentation and deny-by-default rules. Policy changes are version-controlled. Writing the risk analysis and the security policy stays with your team.

Art. 21(2)(b)Incident handling Supports
What NIS2 requires

Prevent, detect and handle incidents, and send an early warning within 24 hours of becoming aware of a significant incident.

How Access Gate addresses it

Access Gate detects session anomalies, sends alerts and replays sessions for forensics. Every connection is logged with user identity, timestamp, source and destination. Incident evidence is recorded continuously and can be exported on demand. Running the response and notifying the authority stay with your team.

Art. 21(2)(c)Business continuity and crisis management Supports
What NIS2 requires

Keep operations running during and after a security incident. Manage backups and disaster recovery.

How Access Gate addresses it

Access Gate connects beside the network. If the appliance is unavailable, production traffic continues. Policy configurations can be exported for backup. Disaster recovery plans stay with you.

Art. 21(2)(d)Supply chain security Enforced
What NIS2 requires

Manage cybersecurity risks in supplier and service provider relationships.

How Access Gate addresses it

Vendor access is scoped per session to specific assets, protocols and time windows, with MFA. Every vendor session is recorded with a full audit trail. The VPN ends at the gate, and no persistent access remains. Access is revoked automatically when the session ends. Supplier contracts and supplier assessments stay with you.

Art. 21(2)(e)Security in system acquisition, development and maintenance Supports
What NIS2 requires

Secure the acquisition, development and maintenance of network and information systems. Handle and disclose vulnerabilities.

How Access Gate addresses it

Access Gate does not handle vulnerabilities. Its passive discovery finds unmanaged devices that your vulnerability process has to cover. It does this without active scanning, which could disrupt OT. Deny-by-default rules limit which connections can reach a machine that is waiting for a patch. Secure development, patching and vulnerability disclosure stay with your team.

Art. 21(2)(f)Effectiveness assessment Supports
What NIS2 requires

Assess the effectiveness of cybersecurity risk management measures.

How Access Gate addresses it

Segmentation baselines, access policy reviews and session log analysis give you data to assess the measures. Evidence packages are generated on demand for auditors and regulators. Running the assessment stays with your team.

Art. 21(2)(g)Cybersecurity hygiene and training Supports
What NIS2 requires

Apply basic cyber hygiene practices and train staff in cybersecurity.

How Access Gate addresses it

Access Gate policies require MFA, least-privilege access and session timeouts. Training content and delivery remain a customer responsibility.

Art. 21(2)(h)Cryptography and encryption Enforced
What NIS2 requires

Set policies and procedures on the use of cryptography and, where appropriate, encryption.

How Access Gate addresses it

Every access path uses TLS, with AES-128/256 GCM and ECDHE key exchange. Encryption is applied at the proxy, with no change to production equipment. Your cryptography policy stays with you.

Art. 21(2)(i)Access control and asset management Enforced
What NIS2 requires

Secure human resources, set access control policies and manage assets.

How Access Gate addresses it

Article 21(2)(i) names asset management. The asset inventory lists every machine from the traffic already on your network, with its history of changes. Access is identity-based, with MFA and RBAC per user, per asset and per protocol. Access policies are enforced at the network layer.

Art. 21(2)(j)Multi-factor authentication Enforced
What NIS2 requires

Use multi-factor or continuous authentication and secured communications, where appropriate.

How Access Gate addresses it

MFA is enforced at the proxy before any session reaches the asset. TOTP tokens work offline for air-gapped sites. Every access path is encrypted with TLS. Secured voice, video and emergency communications stay with you.

How Guichon Valves secured OT and IT for NIS2.

Guichon Valves
100%

of OT-IT flows segmented and auditable for NIS2 compliance. The deployment did not disrupt production.

Trusted by leading companies

Thales
Orange Cyberdefense
John Cockerill
NeverHack
Kyron
Eden Cluster
Ciberlogic
Datasheet

Download the Access Gate Datasheet.

Get the complete product overview with technical capabilities, deployment model, compliance alignment, and customer references.

Done

What's Inside

Product architecture, deployment model, key capabilities (proxy enforcement, micro-DMZs, identity-based access), compliance alignment, and real-world customer deployments.

2 pages

See It in Action

Request a live demo to see how the Access Gate deploys on your network without rewiring or downtime.

Request a demo
FAQ

Common questions about NIS2 for OT.

10

measures in Article 21(2). Access Gate enforces or supports the network part of each one, on site.

Medium and large entities in the 18 sectors of Annexes I and II are in scope: 50 or more employees, or more than €10M in both annual turnover and balance sheet total. Manufacturing in Annex II covers medical devices, computer, electronic and optical products, electrical equipment, machinery, motor vehicles and other transport equipment. Chemicals and food are separate Annex II sectors. Large enterprises in Annex I sectors such as energy and water are essential entities, and most others are important entities. Some entities are in scope whatever their size. For in-scope sites, Trout Access Gate applies the network part of Article 21 to the OT from one appliance per site, connected beside the network.

Article 21(2) requires (a) risk analysis and information system security policies, (b) incident handling, (c) business continuity and crisis management, (d) supply chain security, (e) security in system acquisition, development and maintenance, including vulnerability handling, (f) assessment of the measures' effectiveness, (g) cyber hygiene and training, (h) cryptography and encryption, (i) human resources security, access control and asset management, and (j) multi-factor authentication and secured communications. They apply to OT as much as to IT.

Article 23 sets three steps for a significant incident: an early warning to the CSIRT or competent authority within 24 hours of becoming aware of it, an incident notification within 72 hours, and a final report within one month of the notification. Access Gate logs who reached which machine and when. Your team takes the facts for each report from that log. Notifying the authority stays with you.

Article 21(2)(d) requires supply chain security, including the security of your relationships with direct suppliers and service providers. Points (i) and (j) add access control and MFA. Machine builders and integrators who connect remotely reach only the machines you allow, for a set time and with MFA. Access Gate records every session. Access ends when the session ends. See secure remote access for OT.

It needs one change. You connect Access Gate to your existing firewall or router and add one rule that forwards the machine traffic to it. Removing that rule is the rollback. There is no re-cabling and no IP change, and nothing is installed on the machines. Access Gate is installed in a day.

Yes. NIS2 does not require a cloud service. Access Gate runs entirely inside your perimeter, with no SaaS dependency and no remote control plane. Its logs and policies stay on your network. Operators who want their OT access data under their own jurisdiction keep it there.

Yes, in practice. Article 21(2) does not use the word, but it requires network and information system security measures, basic cyber hygiene and access control. Recital 89 lists network segmentation among those practices. Implementing Regulation (EU) 2024/2690 makes segmentation explicit for digital-sector entities. Access Gate applies zone policies at the network, and nothing is installed on the machines.

The directive requires Member States to provide maximum fines of at least €10M or 2% of total worldwide annual turnover in the preceding financial year for essential entities. For important entities, the floor is €7M or 1.4%. In both cases the higher amount applies. Under Article 20, the management body approves and oversees the measures and can be held liable. For essential entities, Article 32(5) allows authorities, when enforcement measures stay ineffective, to request a temporary ban on a chief executive or legal representative exercising managerial functions.

NIS2 sets the obligations, and IEC 62443 is the industrial standard many OT teams use to meet them. Access Gate applies the IEC 62443 zones and conduits model. The same policies and logs serve as evidence for Article 21 and for an IEC 62443 program. See IEC 62443 for OT.

Start with the gate, then add services on the same appliance.

Secure your plants now, then digitalize them under your control.

Access Gate puts compute on the wire, next to your assets. Once the gate is in, the same box hosts the services that pull OT in securely: remote access, protocol gateways, DNS and time, historian, update server. You speed up digitalization and keep control of it.