Join our Newsletter — 33% off our NHI Course

What should organisations prioritise first in OT and AI-connected environments: segmentation or identity governance?

Identity governance comes first when trusted access paths already exist. Segmentation helps, but it does not remove risk from shared credentials, delegated access, or intermediary services that are already inside the workflow. Practitioners should start with scoped permissions, revocation, and continuous authorization, then layer network controls around that model.

Why identity governance should come before segmentation in OT and AI-connected environments

Segmentation is valuable, but it assumes the access path is already constrained. In OT and AI-connected environments, that is often not true: operators, service accounts, integrations, and AI workflows can already hold valid access that bypasses network boundaries. Identity governance fixes the access model itself, so it has to come first.

The practical difference is that segmentation limits where traffic can go, while identity governance determines who or what can act, under what conditions, and for how long. If permissions are too broad, credentials are shared, or sessions remain valid after role changes, segmentation only reduces the blast radius after access has already been granted. That is why scoped permissions and revocation are the first-order controls.

For readers building this model in practice, the baseline is to treat OT and AI-connected systems as trust chains, not just network zones. A connected historian, orchestration platform, remote support workflow, or AI service can become the route by which legitimate access is abused, so continuous authorization and entitlement review matter as much as traffic filtering.

What changes when identity controls are missing

When identity governance is weak, the environment may look segmented on paper but still behave as a flat trust domain in practice. Shared credentials, static service access, and stale delegated permissions can let one compromised path reach many assets, including systems that operators believe are isolated.

That is especially important in hybrid OT and AI-connected estates where integrations are common. If a connector, bot, or service account can read, write, or trigger actions across multiple systems, the real control point is the identity lifecycle, not the subnet boundary. IAM and IGA Basics is a useful reference point for understanding why authorization, provisioning, and access review have to be designed together.

The same logic applies when access is granted through workflows rather than direct logins. The more delegation and automation you have, the more important it becomes to know which identities are active, which are dormant, and which can still exercise privilege without a current business need.

How to layer segmentation after the identity model is established

Once permissions, revocation, and continuous authorization are in place, segmentation becomes the containment layer rather than the primary defence. That means zone design should reflect real trust relationships, not assumed ones. If an identity can still reach a critical function through a valid token or workflow, the network policy must be aligned to that reality.

In OT environments, this usually means separating operator access, vendor access, service traffic, and machine-to-machine paths so each has a different control profile. In AI-connected environments, it also means distinguishing human users from orchestration services and autonomous workflows. Identity Governance for AI Agents Guide is relevant where autonomous workflows need ownership, lifecycle control, and access review.

Network controls then become sharper because they are enforcing a smaller, better-understood set of allowed relationships. That is the correct order: establish who may act, then confine where that action can occur.

Risk and Threat Considerations

Weak identity governance can create exposure even in well-segmented environments because the attacker does not need to break the network first if they can use valid access that already exists. Shared credentials, overprivileged service accounts, and stale delegated access are common ways for compromise to spread across OT and AI-connected workflows.

Failure mechanism: A valid identity is reused, overextended, or not revoked in time, so segmentation only constrains part of the path while the trusted access relationship remains intact.

Impact: Attackers or insiders can pivot through legitimate integrations, issue unauthorised commands, or reach downstream systems that were assumed to be isolated, increasing operational and safety risk.

Risk and Threat Considerations

When segmentation is treated as the first control, organisations often discover that trust has already been embedded into credentials, APIs, vendors, and automation. That is why the main exposure is not only lateral movement, but persistent authorised access that survives organisational change.

Failure mechanism: Privileged access remains valid across systems because lifecycle control, revocation, and entitlement review were not enforced before network controls were layered on top.

Impact: A compromise or misconfiguration can cascade through OT operations or AI-connected services, where legitimate access paths allow broader action than the segment boundaries suggest.

Practitioner Guidance

Decision rule: If the environment already depends on shared, delegated, or automated access, treat identity governance as the first remediation layer and segmentation as the containment layer.

Implementation sequence: Remove unnecessary access, tighten service and delegated permissions, enforce timely revocation, then validate that segmentation matches the remaining trust relationships.

Practitioner takeaway: The control that changes the trust model belongs first; the control that narrows the blast radius comes second.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5, NIST Zero Trust (SP 800-207) and CIS Controls v8 set the governance and control requirements practitioners need to meet.

Framework Control / Reference Relevance
NIST SP 800-53 Rev 5 IA-5 — Authenticator Management Identity governance in OT and AI-connected access depends on credential lifecycle control.
AC-6 — Least Privilege Scoped permissions are the core recommendation when trusted access already exists.
AC-2 — Account Management Revocation, ownership, and continuous authorization require account lifecycle control.
Recommendation — Rotate, revoke, and track authenticators before relying on network segmentation. Restrict privileges so OT and AI-connected identities can only perform needed actions. Review, disable, and reauthorize accounts on a defined lifecycle cadence.
NIST Zero Trust (SP 800-207) 0 — Zero Trust Architecture The question is about establishing trust through identity before applying network boundaries.
Recommendation — Design access decisions around verified identity and continuous authorization, then segment traffic.
CIS Controls v8 5 — Account Management Account control is central when shared credentials and delegated access exist.
Recommendation — Manage accounts tightly so segmentation is not compensating for uncontrolled access.

Practitioner Guidance

What to prioritise: Start with the identities that can move across environments, not with the network diagram. That includes operator accounts, service accounts, remote access identities, integration users, and AI or automation accounts that can trigger actions in OT-connected workflows.

What to verify: Confirm that every privileged path has an owner, a purpose, a revocation method, and a review cadence. If you cannot answer who can still use the access, under what conditions, and how quickly it can be removed, segmentation is being asked to compensate for a governance gap.

Practitioner takeaway: Use segmentation to contain risk, but use identity governance to prevent trusted access from becoming the hidden bridge around segmentation.