TL;DR: OT environments still rely on local identities, isolated directories and manually maintained access that can outlive HR changes, creating hidden accountability gaps across plants, according to Gathid. The governance problem is not centralisation for its own sake, but visibility that respects operational boundaries while closing stale-access risk.
Editorial analysis by NHI Mgmt Group, based on content published by Gathid: “Beyond Firewalls: How to Fix Identity Gaps In Operational Technology”.
Key questions
Q: What breaks when OT identities are managed only inside local plant silos?
A: Access and accountability drift apart.
Q: Why does OT identity governance create risk even when safety teams resist integration?
A: Because the resistance is usually rooted in legitimate operational safety concerns, not stubbornness.
Q: How do digital twins help with OT access reviews?
A: They let teams analyse access relationships outside the live OT environment.
Practitioner guidance
- Map OT-local identity domains Build an inventory of every plant, facility and segment that maintains its own directory, local accounts or site-specific access policy.
- Reconcile OT access to HR status Compare active OT accounts against employment status, contractor end dates and role changes, then flag identities that still authenticate inside a site after the business relationship has ended.
- Model access in a read-only twin Create an external identity twin from snapshots so teams can analyse OT entitlements, conflicting roles and orphaned accounts without writing back into control systems.
Bottom line: OT identity risk is being created by local access records that outlive the business events meant to close them.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Local OT access outliving corporate lifecycle events is the real governance failure. This article shows that the central risk is not just fragmented infrastructure, but identity records that no longer reflect employment reality. When HR changes do not reach the OT domain, access review loses meaning because the authoritative record and the operational record diverge. Practitioners should treat that mismatch as a governance defect, not an administrative inconvenience.
A question worth separating out:
Q: Who should own OT identity lifecycle decisions across plants and corporate IAM?
A: Ownership should be shared, but accountability must be explicit. Corporate IAM, OT engineering, HR and security all influence the access record, yet no one should be able to defer revocation because another team owns part of the process. The fix is a named lifecycle owner with authority across the full chain.
👉 Read our full editorial: OT identity governance is still stuck in local access silos