IAM for legacy OT: Securing operations without downtime

Implementing a robust Identity and Access Management (IAM) strategy for legacy Operational Technology (OT) is critical for their integration into IoT platforms, demanding a balance between cybersecurity and operational continuity. This article explores architectural approaches to achieve this goal.

The accelerated convergence of Information Technology (IT) and Operational Technology (OT) in industrial environments and smart buildings presents unique cybersecurity challenges. The protection of legacy OT assets, which were not designed for network connectivity or modern identity management, is a particularly acute issue. Ensuring robust Identity and Access Management (IAM) for these devices without disrupting critical operations is a strategic imperative that requires careful architectural and operational planning.

Defining the unique IAM challenges for legacy OT devices

Legacy OT devices, such as SCADA systems, DCS, and PLCs, historically operated in isolation, relying on physical security and proprietary protocols. They often have limited computing resources, memory, and do not support modern cryptographic protocols or sophisticated authentication mechanisms. This creates significant security gaps, as many use outdated operating systems, local accounts, hardcoded credentials, or lack authentication entirely. The long lifecycle of OT equipment, which can span decades, further complicates the implementation of security updates and modern IAM solutions.

The IT/OT convergence expands the attack surface, as legacy OT assets, shared accounts, vendor access, and low visibility hinder consistent identity control. Instead of 'breaking into' systems, attackers can simply 'log in' using vulnerable identity points for both humans and machines. This makes IAM critical for industrial cybersecurity.

Architectural approaches to implementing IAM for legacy OT in IoT platforms

To overcome these challenges, architectural solutions are needed that provide IAM for legacy OT devices without direct modification:

  • Network segmentation with secure gateways and bastion hosts: This approach involves creating micro-perimeters and isolating IT and OT networks. Secure gateways and bastion hosts act as controlled entry/exit points, providing authentication and authorization before connecting to OT assets. They can function as a 'reverse valve,' allowing or denying access based on pre-programmed security policies.
  • Protocol translation with embedded security: Protocol gateways and Unified Namespace (UNS) architectures act as translation layers, normalizing data from various sources into a single event-driven bus. Some modern protocols, such as OPC UA, include built-in certificate-based encryption, TLS encryption, and granular access control. For legacy protocols like Modbus RTU or Modbus TCP, which lack built-in authentication or encryption, security can be added via gateways that support IDaaS (Identity as a Service) policies.
  • Proxy authentication: Proxy servers can require user authentication before authorizing a connection. Identity-aware proxies can add an authentication layer on top of protocols such as Modbus TCP or DNP3. This allows control over access to SCADA systems, for example, granting read-only data access for certain users, while others receive full access after authentication and encryption.
  • Hardware Security Modules (HSM) for new retrofits: Hardware Security Modules (HSM) are specialized cryptographic processors that generate, protect, store, and use cryptographic keys in a secure, tamper-resistant hardware environment. They act as 'trust anchors' for encryption, signing, authentication, and other critical operations. HSMs can be used to protect encryption keys, digital signatures, and authentication, reducing the attack surface as keys remain within the cryptographic boundary, and applications use them without direct access.

Evaluating and selecting the optimal IAM strategy

Choosing the optimal IAM strategy for legacy OT devices requires considering a range of criteria:

Architectural ApproachKey IAM MechanismsSecurity BenefitsImplementation ComplexityImpact on OperationsEstimated Costs
Network Segmentation with Secure GatewaysNetwork isolation, firewalls, bastion hosts, gateway-level access control.Reduced attack surface, prevention of threat propagation, centralized access control.Medium-High (requires network infrastructure changes).Minimal after implementation, potential delays at gateways.Medium (gateway hardware, configuration).
Protocol Translation with Embedded SecurityProtocol gateways, data normalization, built-in security mechanisms (e.g., OPC UA), TLS.Provides authentication and encryption for incompatible protocols, unified data format.Medium (gateway selection and configuration, protocol integration).Low if gateways operate efficiently; potential translation delays.Medium (specialized gateways, licenses).
Proxy AuthenticationProxy servers, pre-access authentication, proxy-level access policies.Adds an authentication layer to devices without native support, granular access control.Medium (deployment and configuration of proxy servers).Low if proxy servers are high-performance; potential delays.Medium (proxy software, hardware).
Hardware Security Modules (HSM) for New RetrofitsGeneration, storage, and use of cryptographic keys in a secure hardware environment.Highest level of key protection, tamper resistance, reduced risk of compromise.High (integration with new or updated devices, key management).Low if integrated at deployment stage; potential maintenance costs.High (HSM cost, integration).

When selecting, it is important to assess the security benefits of each approach, implementation complexity, potential impact on operational continuity, and estimated costs. For example, implementing a Zero Trust architecture in OT environments requires continuous verification of user and device identities, micro-segmentation of control network zones, and context-based access control policies.

Integrating OT IAM into the enterprise cybersecurity strategy

Effective IAM for OT devices must be integrated into a broader enterprise security architecture. This includes centralized Identity and Access Management (CIAM) for hybrid IT/OT environments, enabling the application of unified security policies. Key elements include:

  • Principles of least privilege and Zero Trust: Limiting user and device access only to those resources absolutely necessary for their functions. The Zero Trust model assumes that no user or device is trusted by default, even if they are within the network.
  • Multi-Factor Authentication (MFA) and Role-Based Access Control (RBAC): Applying MFA for all critical systems and assigning permissions based on roles to ensure users and devices have only the necessary access.
  • Auditing and logging: Comprehensive logging of all access events to OT devices is critical for detecting anomalies and responding to incidents.
  • Device identity lifecycle management: Automating the processes of registration, credential issuance, rotation, revocation, and decommissioning of device identities.

These measures help create an identity-centric OT environment that is more resilient to cyberattacks and compliant with modern regulatory requirements.

AZIOT provides a platform for integrating and managing IoT devices, enabling the implementation of the described architectural approaches to ensure IAM for legacy OT devices. Through flexible gateways and protocol translation mechanisms, AZIOT ensures centralized access control and monitoring in a unified interface, supporting integration with MQTT, Modbus, BACnet, SCADA, and other protocols, while leveraging edge computing for enhanced security and efficiency.

Implementing IAM for legacy OT devices is not just a technical task but a strategic decision that requires a deep understanding of both technologies and operational processes. By choosing the right architectural approach and integrating it into the overall cybersecurity strategy, enterprises can significantly enhance the resilience of their critical infrastructures, while ensuring operational continuity and efficiency. It is important to remember that security is a continuous process that requires constant adaptation and improvement.

Learn more about Intecracy and inbase.com.ua solutions to optimize your infrastructure. Intecracy solutions and inbase.com.ua solutions offer a wide range of capabilities.

Source list

  1. medium.com
  2. seguri.ioSeguri | IAM in Operational Technology: Why IT Identity Solutions Don’t Work in Industrial Environments
  3. deviceauthority.comSecuring the Battleground: Moving Beyond Legacy Barriers to Zero Trust for IoT and OT IAM - Device Authority
  4. isc2.orgIT/OT Convergence
  5. nhimg.orgIT/OT convergence and identity gaps in manufacturing security
  6. swidch.comThe Pivotal Role of Identity in OT Cybersecurity
  7. zpesystems.comHow to Implement Zero Trust for OT
  8. opswat.com