Air-gapped OT relies on isolation and physical separation to limit access, while converged IT OT identity management assumes connected environments and governs access through identity controls. In practice, the first reduces exposure by separation, but the second supports modern industrial operations by adding visibility, access review, and revocation across cloud, on premises, and hybrid assets.
Why the two models are not just different levels of the same control
Air-gapped OT is built around separation first: the environment is meant to stay isolated, so access is constrained by network boundaries, removable media policy, and tightly controlled physical pathways. Converged IT OT identity management starts from a different assumption: OT and IT can be connected, but access must be governed through identity, privilege, and lifecycle controls that work across hybrid estates. For a practitioner, the key difference is whether resilience depends mainly on isolation or on continuous control of who can do what.
That distinction changes the operating model. In an air-gapped design, the primary security question is how to preserve the gap and prevent accidental bridging. In a converged model, the question becomes how to make access review, revocation, and delegation reliable enough that connectivity does not become uncontrolled exposure. The second model is not weaker by default, but it requires stronger governance discipline because the trust boundary is no longer a wall, it is a set of enforceable identity decisions.
For a broader control view, NIST SP 800-82 Rev 3 — OT Security Guide frames OT security around architectures, segmentation, and control baselines that help explain why connected industrial environments need explicit trust boundaries.
What changes in exposure, visibility, and recovery
An air-gapped OT design reduces the number of remote paths an attacker can use, but it also limits visibility and makes updates, monitoring, and incident response harder to coordinate. If the environment is truly isolated, compromise usually depends on a physical crossing point, such as media handling, maintenance activity, or a trusted bridge that was never meant to become permanent. The security benefit is reduced exposure, but the operational cost is slower change and less shared telemetry.
Converged IT OT identity management trades some of that isolation for better operational control. Centralised identity lets teams see active accounts, stale privileges, vendor access, and cross-environment entitlements, which matters when production systems depend on cloud services, remote engineers, or shared operational platforms. The downside is that a bad identity decision can now travel farther: one overprivileged account can reach more systems, and one weak review process can leave standing access in place longer than intended.
That is why converged environments need consistent identity governance, not just authentication at the edge. OT and ICS Identity and Access Guide is a useful reference for the OT-specific issues that become visible once access is governed across shared accounts, vendor remote access, and segmented industrial zones.
How practitioners should choose between isolation and convergence
The decision is not “which is safer” in the abstract, it is which operating model matches the plant’s dependency profile and change cadence. Air-gapped OT is strongest where the system can tolerate slow updates, minimal remote support, and strict physical control. Converged IT OT identity management is stronger where uptime depends on faster access decisions, remote operations, and auditable delegation across multiple environments.
In practice, the most common failure is trying to keep the benefits of both models while accepting the governance of neither. Teams keep a nominal air gap but allow informal bridging through laptops, temporary media, or unmanaged support paths. Or they converge connectivity without building the identity lifecycle controls needed to keep vendor, administrator, and service access constrained. Either approach can work, but only if the design intent is clear and the control model matches it.
For readers comparing converged operating models, Identity Convergence Guide helps explain how unified identity control changes governance when once-separate environments start sharing trust and policy.
Risk and Threat Considerations
Air-gapped OT lowers remote attack surface, but it does not remove insider risk, supply-chain exposure, or the risk created by temporary connectivity that becomes routine. Converged IT OT identity management improves visibility and revocation, but it also concentrates trust in identity infrastructure, so a compromise, misconfiguration, or overbroad entitlement can affect more assets at once.
Failure mechanism: In isolated OT, the usual failure is a bridge that bypasses the intended separation, such as unmanaged remote support, rogue media, or a maintenance path that was never tightly governed. In converged environments, the usual failure is privilege accumulation, stale accounts, or inconsistent revocation across IT and OT, which leaves access available after it should have been removed.
Impact: The first model can fail through loss of isolation, while the second can fail through loss of control over delegated access. In both cases, the result is the same business problem: unauthorised reach into systems where safety, availability, and process integrity matter more than convenience.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST CSF 2.0, NIST SP 800-53 Rev 5 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | PR.AA-05 — Identity Management, Authentication, and Access Control | Covers governed access across connected OT and IT environments. |
| Recommendation — Apply PR.AA-05 to enforce identity-based access and timely revocation across OT and IT assets. | ||
| NIST SP 800-53 Rev 5 | IA-9 — Identification and Authentication (Non-Organizational Users) | Relevant to vendor and third-party remote access into industrial environments. |
| AC-6 — Least Privilege | Directly addresses privilege minimisation in converged identity-managed OT. | |
| Recommendation — Use IA-9 to authenticate external users and tightly scope their OT access. Apply AC-6 to limit OT access to the minimum permissions needed for each role. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | Supports access governance where OT and IT are connected and identity-driven. |
| Recommendation — Implement A.5.15 to define and enforce access rules across converged estates. | ||
| CIS Controls v8 | CIS-6 — Access Control Management | Maps to account review, revocation, and privilege control in hybrid OT/IT access. |
| Recommendation — Use CIS-6 to inventory, review, and remove unnecessary access paths. | ||
Practitioner Guidance
What to verify: If the site claims to be air-gapped, verify the physical and procedural paths that still allow files, credentials, firmware, or support access to cross the boundary. If the site is converged, verify that the identity system can prove who has access, why they have it, and how quickly it can be removed.
Decision rule: Use isolation when operational requirements truly allow it, but do not treat a paper air gap as a substitute for access governance. If the environment needs remote administration, hybrid monitoring, or shared industrial services, treat identity controls as part of the control plane, not as an afterthought.
Practitioner takeaway: The real choice is between boundary security and governed connectivity, and the winning design is the one whose control model still works when the environment is stressed, changed, or partially compromised.
Related resources from NHI Mgmt Group
- Guide: EBA ICT and Security Risk Guidelines Guide
- Why do air-gapped deployments create identity governance risk?
- What fails when organisations treat OT as air-gapped in practice?
- How should financial institutions use converged identity and access management to support digital transformation without weakening security?
- What do teams get wrong when they assume OT networks are air-gapped or off-grid?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 4, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org