How does implementing secure authentication at each OT endpoint strengthen an organization’s overall cyber defense posture?
OT endpoints — often shared workstations or legacy systems — are typically not designed with modern security in mind. In fact, passwords and PINs are frequently reused or shared among frontline workers, making them easy targets for attackers. Implementing secure authentication methods such as smart card readers and biometric readers ensures that only authorized personnel can access critical systems.
These methods provide non-repudiation, ensuring accountability for actions taken on OT systems, resistance to credential theft, as smart cards or biometrics cannot be easily duplicated or phished, and compliance with zero trust principles, which require strong identity verification before granting access.
What are the operational or security risks of continuing to rely on traditional passwords in OT environments?
Traditional passwords are one of the most exploited attack vectors in OT breaches, and even strong passwords can be phished, guessed, or stolen. Additionally, PINs are just as unsecure as passwords as they can also be easily compromised or guessed. CISA advises changing default credentials and using strong passwords by removing the password attack surface entirely.
The Case for Modern Authentication
Can you explain how passwordless authentication methods, such as Passkeys, work and why they may be a better fit for OT systems?
Passkeys — cryptographic credentials tied to a user’s device and biometric identity — offer a phishing-resistant alternative to passwords. Passwords remain one of the most exploited attack vectors in OT breaches and even strong passwords can be phished, guessed, or stolen. Passkeys prevent credential reuse across systems, eliminate the risk of password theft via keyloggers or phishing and simplify user experience while enhancing security.
Additionally, passkeys can enable unique individual credentials within shared workstations and accounts, thus boosting accountability. Overall, passkeys are a better, more secure fit for OT systems than traditional passwords.
Multi-factor authentication (MFA) is often discussed in IT circles. How should it be adapted or implemented for OT systems with unique constraints?
Multi-factor authentication should be implemented across all critical systems and access points, including local OT workstations, engineering workstations, SCADA, PLC and HMI interfaces and business applications that interface with OT systems. In doing so, systems ensure that even if one factor — such as a password or proximity card — is compromised, unauthorized access is still blocked. Using phishing-resistant MFA, like FIDO2 tokens or biometric-based MFA, is especially critical in high-risk environments.
What practical challenges do OT teams face when trying to implement modern authentication methods, and how can they overcome them?
OT teams face several practical challenges when trying to implement modern authentication methods like MFA, single sign-on (SSO), or certificate-based authentication. These challenges stem from the unique nature of OT environments, which differ significantly from traditional IT systems.
Many OT systems were designed decades ago and lack support for modern authentication protocols (like SAML, OAuth, or even LDAP). There are two main ways this can be solved. First, OT teams can use protocol translation gateways or identity-aware proxies to bridge modern IAM systems with legacy OT devices. Alternatively, OT teams can implement network segmentation to isolate legacy systems and apply compensating controls like jump servers with MFA.
Another significant challenge is the needs of remote access. Remote maintenance and monitoring are common in OT, but they introduce authentication risks. OT teams should enforce MFA for all remote access or use zero trust network access (ZTNA) or VPNs with strong identity verification.
OT systems can also come with high uptime requirements. OT systems often run 24/7 and cannot afford downtime for authentication system upgrades or failures. A way to solve this is to use offline-capable MFA solutions (like smart cards) that don’t rely on internet connectivity. Additionally, OT environments often have fragmented identity systems or shared accounts. OT teams need to implement either centralized identity stores (like Active Directory) with role-based access control (RBAC) or unique credentials within shared workstations and accounts to enforce individual accountability.
First Steps Toward Stronger OT Access Control
For critical infrastructure operators looking to strengthen authentication protocols, what are the first two or three steps you’d recommend they take today?
For critical infrastructure operators aiming to strengthen their authentication protocols, the first step is to conduct an authentication risk assessment or audit. Organizations need to understand where their current authentication practices are weakest, especially in OT environments where legacy systems and shared accounts/workstations are common. It’s also important to enforce MFA for all access.
MFA is one of the most effective defenses against credential-based attacks, especially for remote access and administrative accounts. Finally, I’d recommend implementing unique credentials within shared accounts and workstations to make it possible to trace actions to individuals.