Two operators at a control-room desk with a row of monitors, a laptop and keyboards

OT/ICS security

OPC UA security: built in, often unused, and what breaks when it is

Last updated:

OPC UA (OPC Unified Architecture, standardized as IEC 62541) is unusual among OT/ICS protocols for a specific reason: its own specification treats security as a core design objective, with defined authentication, message-signing and encryption modes — not a bolt-on add-on specification the way Modbus and DNP3 treat their security options. And yet CISA keeps publishing critical OPC UA advisories, and CISA's own 2026 research found most OT operators still aren't turning the built-in security on. Both things are true at once, and understanding why is the difference between picking OPC UA because "it's the secure one" and actually operating it securely.

Specification quotes come from the OPC Foundation's reference site (OPC 10000-2 v1.05.06 and companion parts) and its profiles database; advisory facts from CISA's CSAF files and the OPC Foundation's own bulletins; the CISA report from its February 2026 PDF. All were read on 12 November 2026.

Key takeaways

  • The spec is also explicit about defaults.
  • Part 7 points to the OPC Foundation's online profiles database, which records each SecurityPolicy's release status.
  • OPC UA authenticates two different things.
  • Sources: cisagov CSAF (ICSA-26-211-08 JSON) and the OPC Foundation's security advisories repository, read 12 November 2026.

What does OPC UA's own spec actually require?

Per OPC 10000-2 ("OPC Unified Architecture — Part 2: Security Model", v1.05.06, also published as IEC 62541-2:2026), Section 4.2 defines the security objectives the protocol is designed around, among them Authentication ("Entities such as Clients, Servers, and users should prove their identities"), Authorization ("The access to read, write, or execute resources should be authorized for only those entities that have a need for that access"), Confidentiality ("Data is protected from passive attacks such as eavesdropping, whether the data is being transmitted, in memory, or being stored"), Integrity ("Receivers receive the same information that the original sender sent, without the data being changed during transmission"), Non-Repudiation, Auditability, Availability and Perfect Forward Secrecy. Section 4.8 operationalizes these into a MessageSecurityMode every session negotiates: None, Sign, or SignAndEncrypt. A companion specification, Part 7, defines the actual SecurityPolicy URIs (cryptographic algorithm suites) a server and client can agree on.

The spec is also explicit about defaults. Section 4.7 says "Profile 'None' provides no security", and Section 4.8 says "Profile None shall be disabled by default." Where data confidentiality is not required, 4.8 allows that "'Sign' is sufficient." This is a meaningfully different starting point from a protocol like Modbus, whose base Application Protocol specification has no equivalent section at all — see Modbus protocol security: why it has none for that comparison in full.

Which SecurityPolicies are current, and which are deprecated?

Part 7 points to the OPC Foundation's online profiles database, which records each SecurityPolicy's release status. As of 12 November 2026 (UA Core 1.05 profiles):

SecurityPolicy (URI suffix) Status Note from the profiles database
None Released "By default this security policy shall be disabled if any other security policy is available."
Basic128Rsa15, Basic256 Deprecated SHA-1 "is not considered secure anymore"; deprecated with spec 1.04; if included, "It shall be disabled by default"
Basic256Sha256 Released "no published end dates as of this time"
Aes128_Sha256_RsaOaep, Aes256_Sha256_RsaPss Released Current RSA policies
ECC_nistP256, ECC_nistP384, ECC_brainpoolP256r1, ECC_brainpoolP384r1 Deprecated Replaced by *_AesGcm and *_ChaChaPoly variants (for example ECC_nistP256_AesGcm)
ECC_curve25519, ECC_curve448 Deprecated "It shall not be supported by any application."
RSA_DH_AesGcm, RSA_DH_ChaChaPoly Released New RSA with Diffie-Hellman policies

The ECC changes came with specification 1.05.07. The open62541 project's v1.5.5 release notes (28 June 2026) describe them as "significant changes to the handling of ECC SecurityPolicies." A device that shipped ECC support in 2024 may need a firmware update to stay on a released policy.

How do applications and users prove who they are?

OPC UA authenticates two different things. The application, client or server, proves itself with its X.509 application-instance certificate when the SecureChannel opens. That is what Sign and SignAndEncrypt protect. The user then proves itself inside the session, with one of four token types that OPC 10000-4 §7.40 defines:

  • AnonymousIdentityToken: "No user information is available."
  • UserNameIdentityToken: "A user identified by user name and password." The client must encrypt the token if the token policy's SecurityPolicy requires it.
  • X509IdentityToken: "A user identified by an X.509 v3 Certificate."
  • IssuedIdentityToken: "A user identified by a token issued by an external Authorization Service", such as a JSON Web Token.

Certificates need a lifecycle, and OPC 10000-12 defines one through a Global Discovery Server (GDS) and CertificateManager. In PullManagement, the application acts as a client and requests its own certificates and trust lists. In PushManagement, the CertificateManager calls methods on the server to update them. Both cover onboarding, renewal, trust-list updates and revocation. A device that supports push management can be re-keyed in the field without an engineer copying files by hand.

Where does the built-in security still fail?

A security model in the spec only protects a deployment if the code implementing it is itself correct, and OPC UA stacks have had the same class of memory-safety findings that affect any protocol parser handling untrusted network input:

Advisory Product CVE(s) CVSS What it actually allowed
ICSA-22-242-10 (30 Aug 2022) PTC Kepware KEPServerEX (also OEM'd as Rockwell KEPServer Enterprise, GE Digital Industrial Gateway Server, Software Toolbox TOP Server) CVE-2022-2825, CVE-2022-2848 9.8, 9.1 Specifically crafted OPC UA messages could crash the server and, for the stack-based overflow, remotely execute code; CISA describes the heap overflow (CVE-2022-2848) as a crash and data leak, while NVD and ZDI-22-1454 describe code execution as SYSTEM
ICSA-26-211-08 (30 Jul 2026) open62541 (open-source OPC UA stack, o6 Automation GmbH; versions 1.3.0–1.3.17, 1.4.0–1.4.16, 1.5.0–1.5.4 and master) CVE-2026-63362, CVE-2026-65423, CVE-2026-63035, CVE-2026-63559 up to 8.8 (v3.1) / 8.7 (v4.0) Remote denial of service via crafted PubSub UDP packet, out-of-bounds write via integer overflow, and an authenticated use-after-free able to cause DoS or arbitrary code execution
OPC Foundation bulletins (9 Feb 2025) OPC Foundation UA .NET Standard stack CVE-2024-42512, CVE-2024-42513 5.9, 6.5 (OPC Foundation bulletin scores); 8.6, 5.3 (CISA-ADP scores on the CVE record, shown by NVD) Bypass of application authentication via Basic128Rsa15, and authentication bypass via HTTPS endpoints; fixed in 1.5.374.158

Sources: cisagov CSAF (ICSA-26-211-08 JSON) and the OPC Foundation's security advisories repository, read 12 November 2026. Scores for the two .NET CVEs differ by scorer: CISA-ADP values read from the CVE record on 18 November 2026, and CISA's ICSA-25-072-09 for Siemens products gives 7.4 and 9.1.

CISA's open62541 advisory names no fixed version. The project's v1.5.6 release notes, like those of v1.3.19 and v1.4.18 (all 27 July 2026), list the matching fixes, so those are the versions to check for. Most of these bugs run inside the message-parsing and service-dispatch code, which in some cases executes before — or independent of — whether a session negotiated Sign, SignAndEncrypt, or authenticated with a valid certificate at all. A correctly configured security policy narrows who can reach that code; it does not patch the code itself.

The research record is long. The German BSI's first OPC UA study (work done in 2015, published 2016, per its study page) analysed specification 1.02 and the OPC Foundation's ANSI C reference stack. Its 2022 update, by Fraunhofer, reviewed version 1.04 "mostly based on the open62541 library" and found from a user survey that "products still do not meet the expectations in all security relevant areas." Kaspersky ICS CERT reported on 10 May 2018 "17 zero-day vulnerabilities in the OPC Foundation's products". Claroty's Team82, releasing its OPC UA exploit framework on 9 August 2023, said it had helped find "close to 50 vulnerabilities". Treating "we use OPC UA" as a security property on its own is a mistake; the protocol's security model is only as good as the specific stack's patch level.

Why is the security so often switched off?

CISA's 10 February 2026 report "Barriers to Secure OT Communication: Why Johnny Can't Authenticate" lists the OPC Foundation among its research partners, alongside Anybus, the DNP Users Group, NSA, ODVA, Rockwell Automation, Schneider Electric, the Modbus Organization and Xylem. It names "OPC DA to OPC Unified Architecture [UA]" as one of the secure protocol upgrades that "have existed since the early 2000s", and then asks why organizations are not implementing them. Its answers come from interviews with operators in water and wastewater, transportation, chemical, energy, and food and agriculture, under three headings:

  • "Costs Delay Adoption": procurement, then deployment and maintenance.
  • "Availability Concerns Delay Security Adoption": fears about observability, latency and bandwidth, and confidence. "The two main barriers were cost and the availability concerns stemming from encrypting data."
  • "PKI Difficulties Dissuade Operators": complexity during provisioning and operations, plus connectivity risks.

The observability fear is specific: interviewees "generally assumed that secure communication means that all traffic is encrypted", which complicates inspection. For OPC UA, that plays out as servers and clients that fully support SignAndEncrypt and certificate-based authentication shipping, and staying, on SecurityPolicy: None. OPC UA already has the answer CISA recommends: Sign mode keeps payloads readable to monitoring tools while proving integrity. CISA tells owners to "consider a phased approach beginning with signing only and not dropping packets".

What should a device maker ship by default?

The OPC Foundation's Practical Security Recommendations (Version 3, June 2018), the spec defaults above and CISA's manufacturer list (which starts with "Default to the secure option for all configurations") add up to a short checklist:

  • None disabled by default. The white paper puts it bluntly: "The SecurityMode 'None' does not provide any protection!"
  • Sign or SignAndEncrypt only, with a released policy. "At a minimum, the SecurityPolicy 'Basic256Sha256' should be chosen"; leave Basic128Rsa15, Basic256 and the old ECC policies off.
  • No automatic trust. "Self-signed certificates should not be trusted automatically, i.e., without an additional verification"; use trust lists and revocation lists.
  • Protected keys. "Never store private keys … on an unencrypted file system."
  • Anonymous access only for non-critical data, and user tokens encrypted.
  • GDS push management so customers can rotate certificates, and crypto agility so policies can change by firmware update, which CISA asks for "to remove the fear of buying at the wrong time."
  • Certification by an OPC Foundation accredited test lab; the CTT is a self-test tool, and SDKs cannot be certified on their own.

These map directly to IEC 62443-4-2 component requirements on authentication, communication integrity and PKI.

Can you check an OPC UA deployment passively?

Yes, partly. OPC UA binary runs on TCP port 4840, which IANA registers as opcua-tcp (4843 is opcua-tls). Every SecureChannel opens with an OpenSecureChannel message whose asymmetric security header carries the SecurityPolicyUri and the sender's certificate (OPC 10000-6, Table 58). Encryption starts after that header, so a passive sensor can read which policy each client asked for, even on encrypted channels. CISA's ICSNPP-OPCUA-Binary Zeek parser logs that sec_policy_uri and the requested message_security_mode, plus GetEndpoints and CreateSession details. Flag any channel that opens with policy None or a deprecated policy, any endpoint list that still offers None, and anonymous sessions on servers that write to the process.

What should an asset owner or device maker check first?

  1. Check the negotiated SecurityPolicy and MessageSecurityMode on every OPC UA endpoint you operate, not just whether the product "supports" securityNone is a valid, spec-defined configuration state — and a common default — not something you can assume is off.
  2. Patch the stack, separately from configuring the policyThe Kepware, open62541 and UA .NET Standard CVEs above are implementation bugs that a correctly set SignAndEncrypt policy does not, by itself, fix. Device makers embedding open62541 should be on 1.3.19, 1.4.18, 1.5.6 or later.
  3. Treat certificate lifecycle as an operational process, not a one-time setup stepOPC UA's authentication model depends on X.509 certificates staying valid, trusted and properly rotated — an expired or improperly validated chain silently degrades the same security the spec provides.
  4. Budget for PKI, deliberately, rather than letting cost be the reason security stays offCISA's own research puts cost first among the reasons operators don't enable secure communication; naming that cost during procurement, rather than discovering it during an incident, is the cheaper path.

OPC UA getting the authentication and encryption objectives into its own specification is real progress over protocols like Modbus, DNP3 and classic OPC DA — but CISA's advisory record shows that progress only pays off when the specific stack is patched and the security policy is actually turned on. SoftWSP's OT Snapshot reads Zeek and ICSNPP logs from a recorded capture and lists which hosts talk to which, on which ports, so OPC UA servers show up as hosts with TCP 4840 connections, plus remote-access sessions that cross from outside the private address range. Its parsers do not decode OPC UA, so it does not report the negotiated policy; use the passive check above for that. Stack versions come from a component list or a firmware SBOM, which is how an embedded open62541 version shows up. SoftWSP matches those against NVD, CISA KEV, FIRST EPSS and CISA's ICS advisories, a watchlist can alert on a product or CVE, and an engineer reviews every AI-drafted, cited report before it is sent.

This guide draws on the OPC Foundation's published specification text and profiles database, its security white paper and bulletins, CISA's ICS advisories and February 2026 report, the BSI, Kaspersky ICS CERT and Claroty Team82 publications, open62541 release notes and CISA's ICSNPP parser. It is not a substitute for the OPC Foundation's own specifications, CISA's own advisories and reports, or an engineer's assessment of a specific deployment's configuration and patch level.

Put this guide to work

Frequently asked questions

Does OPC UA actually have security built into the protocol, unlike Modbus?

Yes, and this is the single biggest architectural difference from legacy OT protocols. OPC UA's own Part 2 specification (OPC 10000-2, the Security Model) defines security as a first-class objective of the protocol, not an add-on: Section 4.2 lists Authentication ("Entities such as Clients, Servers, and users should prove their identities"), Authorization, Confidentiality ("Data is protected from passive attacks such as eavesdropping, whether the data is being transmitted, in memory, or being stored"), Integrity, Auditability and Availability as objectives the protocol is built to support. Section 4.8 defines three MessageSecurityMode values any OPC UA session negotiates: None, Sign, and SignAndEncrypt. This is a genuinely different starting point from Modbus or classic OPC DA (which inherited Microsoft DCOM's security model and effectively none of its own) — see [Modbus protocol security](/guides/modbus-protocol-security-ot-ics/) for the contrast with a protocol that has no equivalent objectives in its specification at all.

If the security is built in, why does CISA keep publishing OPC UA vulnerability advisories?

Because having a security model in the specification does not mean every implementation gets it right, and does not mean every deployment turns it on. CISA's advisory ICSA-22-242-10 (30 August 2022, updated 8 September 2022) covers PTC's Kepware KEPServerEX — an OPC UA server embedded, white-labeled or OEM'd into Rockwell Automation's KEPServer Enterprise, GE Digital's Industrial Gateway Server, Software Toolbox's TOP Server and ThingWorx products — and assigns CVE-2022-2825 (CVSS v3 base score 9.8, CWE-121 Stack-based Buffer Overflow) to a finding that "specifically crafted OPC UA messages transmitted to the server could allow an attacker to crash the server and remotely execute code," plus CVE-2022-2848 (CVSS v3 9.1, CWE-122 Heap-based Buffer Overflow), which CISA describes as letting an attacker "crash the server and leak data," while NVD's description, from ZDI, says an unauthenticated attacker can "execute code in the context of SYSTEM." More recently, CISA's advisory ICSA-26-211-08 (30 July 2026) covers four vulnerabilities in open62541 — the widely embedded open-source OPC UA stack maintained by o6 Automation GmbH — including CVE-2026-65423 (integer overflow in variant array-dimension handling, CVSS v3.1 8.8 / CVSS v4.0 8.7, CWE-190) described as able to "trigger an out-of-bounds write," and CVE-2026-63035 (heap use-after-free in the TransferSubscriptions service, CVSS v3.1 8.1, CWE-416) that "may allow an authenticated attacker to cause a denial of service or potentially execute arbitrary code." None of these are failures of the OPC UA security *model* — they are memory-safety bugs in specific stack implementations, the same class of defect that affects any sufficiently complex parser regardless of what the protocol spec says about authentication.

Why would anyone deploy OPC UA without turning its security on?

CISA's own 2026 research into this question, published jointly with the OPC Foundation and other protocol maintainers, found the barrier isn't awareness — it's practical deployment friction. The report "Barriers to Secure OT Communication: Why Johnny Can't Authenticate" (CISA, 10 February 2026; the OPC Foundation lists itself alongside Anybus, the DNP Users Group, NSA, ODVA, Rockwell Automation, Schneider Electric and the Modbus Organization as a contributor) is based on CISA's own interviews with OT asset owners and operators across water/wastewater, transportation, chemical, energy and food-and-agriculture sectors. *This guide draws on the OPC Foundation's own published confirmation that it contributed to the report and its stated publication date, cross-checked against secondary industry reporting (Automation.com, Industrial Cyber). The framing below is a good-faith summary drawn from the OPC Foundation's confirmation and secondary industry reporting (Automation.com, Industrial Cyber); CISA's own PDF is the authoritative source.* With that caveat, the research reportedly groups the barriers into three categories that line up closely with why a security policy of None remains common even on OPC UA deployments that fully support stronger options: cost (procurement, deployment and ongoing maintenance of a PKI), availability fears (operators worried that enabling signing or encryption will add latency or break uptime on a system with no appetite for unplanned downtime), and PKI complexity itself (certificate provisioning and lifecycle management on devices that were never designed to be re-keyed in the field).

What should an asset owner or device maker actually check when using OPC UA?

Three separate things, because "we use OPC UA" says nothing on its own about security posture. First, the negotiated SecurityPolicy and MessageSecurityMode for every endpoint — OPC UA's Part 7 profiles define a None policy specifically so a server can be stood up without any cryptography at all, and that policy remaining enabled (or being the default a device ships with) is a configuration choice, not a protocol limitation; CISA's and the OPC Foundation's own recurring guidance is to disable None wherever a client supports better. Second, the stack's patch level against known CVEs like those in Kepware KEPServerEX and open62541 above — a correctly configured SecurityPolicy does not protect against a memory-corruption bug in the message parser that runs before authentication is even checked. Third, certificate lifecycle: OPC UA's security model depends on X.509 certificate-based mutual authentication between client and server, which means an expired, self-signed, or improperly validated certificate chain can silently degrade the same security the protocol was designed to provide. See [NIST SP 800-82: OT security](/guides/nist-sp-800-82-ot-security/) for where this certificate and patch-management discipline sits inside a broader OT security program, and [the Purdue Model for OT/ICS network architecture](/guides/purdue-model-ot-ics-network-architecture/) for the segmentation that should still apply regardless of what an individual OPC UA endpoint is configured to do.

Sources

  1. OPC Foundation / OPC-10000-2: OPC Unified Architecture — Part 2: Security Model (reference.opcfoundation.org, v1.05.06)
  2. CISA ICS Advisory ICSA-22-242-10: PTC Kepware KEPServerEX (30 August 2022, updated 8 September 2022; CVE-2022-2825, CVE-2022-2848)
  3. CISA ICS Advisory ICSA-26-211-08: o6 Automation open62541 (30 July 2026; CVE-2026-63362, CVE-2026-65423, CVE-2026-63035, CVE-2026-63559)
  4. OPC Foundation: Security (advisories index, BSI OPC UA security analyses, Kaspersky Labs 2017 findings, and CISA's Barriers to Secure OT Communication contribution)
  5. CISA: Barriers to Secure OT Communication: Why Johnny Can't Authenticate (10 February 2026)
  6. OPC 10000-2 §4.8 Security Mode settings (reference.opcfoundation.org, v1.05.06)
  7. OPC Foundation: UA Profiles database (SecurityPolicy facets and deprecation status)
  8. OPC Foundation Security Working Group: Practical Security Recommendations for building OPC UA Applications (Version 3, June 2018)
  9. OPC Foundation: OPC-SecurityAdvisories repository (security bulletins for OPC Foundation code)
  10. BSI: OPC UA security analysis study page (first study, 2015 work, published 2016)
  11. BSI / Fraunhofer: OPC UA Security Analysis, update based on OPC UA 1.04 and open62541 (2022)
  12. Kaspersky ICS CERT: OPC UA security analysis (10 May 2018)
  13. Claroty Team82: OPC UA Deep Dive Series (Part 6), OPC UA exploit framework (9 August 2023)
  14. open62541 v1.5.6 release notes (27 July 2026)
  15. cisagov CSAF: ICSA-26-211-08 machine-readable advisory (30 July 2026)
  16. cisagov ICSNPP-OPCUA-Binary Zeek parser
  17. IEC 62541-2:2026, OPC Unified Architecture — Part 2: Security Model (IEC webstore)
Was this guide helpful?

In this cluster