Topic starter
06/06/2026 11:34 am
TL;DR: SCADA systems now connect HMIs, PLCs, RTUs, enterprise platforms, and vendor remote access, which expands attack surface and makes identity governance central to manufacturing cybersecurity, according to Imprivata and IDC. Legacy OT assets and shared access practices turn connectivity into operational risk; isolation is no longer a sufficient control model.
Editorial analysis by NHI Mgmt Group, based on content published by Imprivata: “SCADA security: Best practices for evolving your manufacturing technology”.
Key questions
Q: What breaks when SCADA systems still rely on shared operator accounts?
A: Shared operator accounts break accountability, make forensic analysis harder, and turn access review into guesswork because no single person is tied to the action.
Q: Why does persistent vendor access increase SCADA risk?
A: Persistent vendor access creates a standing trust path into production systems, which means a maintenance account can outlive the job it was created for.
Q: How should manufacturers govern identity across IT and OT environments?
A: Manufacturers should use one identity governance model across IT and OT, but enforce it through SCADA-specific controls such as unique user identities, role scoping, monitored vendor sessions, and controlled gateways for legacy devices.
Practitioner guidance
- Replace shared HMI logins Give each operator and engineer an individual identity, then map roles to only the SCADA functions required for that job.
- Time-box vendor remote access Approve vendor sessions only for the maintenance window, require session recording, and revoke access immediately after the task ends.
- Wrap legacy PLC and RTU access Place older PLCs and RTUs behind controlled gateways or jump hosts so modern authentication and monitoring can be enforced outside the device.
Bottom line: SCADA environments now depend on governed identity paths because shared access and persistent vendor connections undermine accountability and increase production risk.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/06/2026 12:27 pm
Identity is now the SCADA control plane: once OT systems connect to enterprise platforms and remote vendors, isolation stops being the primary security boundary. The real question becomes who can authenticate into HMI, PLC, and RTU workflows, under what role, and for how long. Manufacturers that still think of SCADA security as a network-segmentation problem are governing the wrong layer. The implication is that production resilience now depends on access governance, not perimeter assumptions.
A question worth separating out:
Q: When do network segmentation and identity controls work best together in SCADA?
A: They work best when segmentation limits where access can reach and identity controls determine who may use the path. Segmentation without strong authentication still leaves a broad trust problem, while identity without segmentation can leave too much lateral movement once access is granted. The two controls are complementary, not interchangeable.
👉 Read our full editorial: SCADA cybersecurity now depends on identity control, not isolation