They need to be planned together whenever privileged administration, remote connectivity or shared infrastructure sits between enterprise IT and operational systems. In those cases, access ownership determines what can be observed, and monitoring coverage determines whether access can be proven and investigated after the fact.
Why monitoring and access governance have to be designed as one control plane in OT
In OT, monitoring cannot be treated as a separate visibility project if privileged administration, remote connectivity or shared infrastructure crosses the boundary between enterprise IT and operational systems. The people and systems that can reach the environment also shape what can be seen, logged and attributed. Access ownership and monitoring coverage therefore need to be designed together, not handed to separate teams in isolation.
That is especially true where remote support, vendor access, jump hosts, shared admin paths or converged infrastructure are part of the operating model. If you cannot tie an action to a governed identity or account, telemetry may show activity but not who controlled it. If you cannot observe the path, access approvals may exist on paper but remain weak evidence after an incident.
In practical terms, the question is not whether OT needs monitoring or access control. It is whether both controls cover the same administrative paths, the same remote entry points and the same shared assets, so that the organisation can answer two questions at once: who was allowed in, and what did they do once inside?
How access ownership determines what monitoring must see
When access is centrally owned, monitoring can be targeted at the identities, sessions, devices and conduits that actually matter. When access is fragmented across plants, vendors and local engineering teams, monitoring often becomes incomplete because no one has authoritative knowledge of which accounts exist, which are still active, or which paths are legitimate.
That gap matters because OT access is often indirect. Remote administration may traverse a bastion, a VPN, a jump server, a shared workstation or a maintenance account before it reaches the control environment. Monitoring that only watches the final destination misses the control points where authentication, approval and session accountability should be enforced. A useful OT and ICS Identity and Access Guide treats those paths as part of the access model, not as a separate IT concern.
That same design issue appears in broader governance work. IAM and IGA Basics explains the access governance side of the problem: if you cannot define ownership, entitlement and review for the accounts that reach OT, monitoring will not reliably tell you whether the right subject used the right access at the right time.
For OT programmes, that means access governance should determine the minimum monitoring scope from the start. The inventory of privileged accounts, remote paths and shared access points becomes the monitoring map. Without that map, logging can be noisy while still missing the events that matter most.
What breaks when you separate visibility from governance
Separation creates a common failure pattern: the access team approves a path that the monitoring team cannot inspect, or the monitoring team deploys sensors around assets that no one has formally assigned or reviewed. In both cases, the organisation loses provable accountability. The result is not just weaker detection, but weaker investigation, because post-event analysis depends on knowing which account, session or support path was in play.
This is also where shared OT infrastructure becomes a governance issue, not only a technical one. A single admin channel used for multiple plants, multiple vendors or both IT and OT services can collapse segregation of duties and make activity attribution ambiguous. The Segregation of Duties (SoD) Guide is relevant here because a shared control path with no clear separation can allow one person or one process to approve, execute and conceal changes too easily.
Visibility and governance should also be aligned when the environment includes discovery or inventory limitations. If OT asset visibility is poor, monitoring may not know which assets should emit logs or which network flows are abnormal. The OT Asset Visibility Guide is useful because it ties inventory, monitoring and criticality together rather than treating them as separate tasks.
The operational consequence is simple: a control that cannot identify the actor, the path or the target is not enough for incident response in OT. Likewise, a governance process that cannot prove observability is incomplete.
Risk and Threat Considerations
OT programmes face material exposure when privileged access exists without matching visibility, because an attacker or careless insider can use a legitimate channel to alter systems, hide activity or move laterally through trusted infrastructure. The risk is highest when shared admin paths, vendor remote access or weakly governed jump hosts sit between enterprise IT and operational networks.
Failure mechanism: Access is granted through accounts or conduits that are not tightly owned, reviewed or session-monitored, so the environment can record activity without reliably attributing it or detecting misuse in time.
Impact: An organisation may fail to prove who performed a change, miss unsafe commands or configuration drift, and lose confidence in both incident reconstruction and day-to-day control over OT operations.
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 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-2 — Account Management | OT access paths and privileged accounts must be owned and reviewed. |
| AU-2 — Audit Events | Monitoring must capture the OT actions needed to prove and investigate access. | |
| AC-17 — Remote Access | Remote connectivity is a primary OT trust boundary that needs access and monitoring together. | |
| Recommendation — Inventory OT accounts and review their access on a defined schedule. Define OT audit events for remote admin, privilege use and configuration change. Restrict and monitor remote OT access through controlled entry points. | ||
| CIS Controls v8 | CIS-5 — Account Management | OT privileged access depends on knowing who can reach shared systems and support paths. |
| CIS-8 — Audit Log Management | OT monitoring must preserve evidence for later investigation of privileged activity. | |
| Recommendation — Maintain a complete inventory of OT admin and remote-access accounts. Centralise and retain OT logs from the systems that mediate privileged access. | ||
Practitioner Guidance
What to prioritise: Start with the privileged and remote paths that can reach operational systems, then define who owns each path, which session evidence is required, and where logs must be collected to prove use. If a path is shared, treat that as a design exception that needs explicit compensating control, not as a normal operating shortcut.
What to verify: Confirm that every approvalable OT access path has a corresponding monitoring source, and that the monitoring can distinguish the actor, the session and the target asset. If those three cannot be connected during an incident review, the control design is not complete enough for OT.
Practitioner takeaway: In OT, monitoring is only defensible when it is built around governed access paths, because visibility without ownership is hard to trust and ownership without visibility is hard to prove.
Related resources from NHI Mgmt Group
- What is the difference between role-based access and API key governance for NHI security?
- What does the 144:1 NHI-to-human ratio mean for IAM governance programmes?
- How do metadata and access governance work together in AI programmes?
- How should security teams run access reviews for non-human identities?