Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is OPC UA Security?

OPC UA is the modern industrial interoperability standard and the only widely deployed one with real security built in, which makes its most common failure a deployment configured to use none of it.

Illustration for the cybersecurity term OPC UA Security
Home / Blog / Cybersecurity Terms / What Is OPC UA Security?
17 November 2026

What Is OPC UA Security?

What Is OPC UA Security?

OPC UA, standardised as IEC 62541, is the industrial world’s answer to the question of how a controller, a historian, a manufacturing execution system, and a cloud analytics platform can exchange data without a bespoke integration for every pair. It replaced OPC Classic, which was built on Microsoft DCOM and therefore tied to Windows, impossible to route through a firewall sensibly, and dependent on domain trust.

What distinguishes OPC UA among industrial protocols is that security was designed in rather than bolted on. Unlike Modbus or base DNP3, it has application identity, mutual authentication, message signing, encryption, user authentication, and audit events as part of the specification. The common failure mode is therefore not a protocol weakness but a deployment that switches all of it off.

The Security Model

Three layers work together:

Servers also emit audit events for session creation, certificate rejection, and configuration change, which is unusual and valuable in an industrial protocol.

Why Deployments End Up Insecure

Certificate management is the reason. When a client first connects to a server, both certificates are untrusted, and someone must move them into the correct trust and rejected folders on both machines. At commissioning, with a plant to hand over and an integrator on site for one more day, the shortest path is to set the endpoint to security policy None with anonymous login and move on. Nobody comes back to it.

The result is a protocol with excellent security capability running with none of it enabled, frequently with an endpoint discoverable on port 4840 and reachable from the business network because the historian or the manufacturing execution system needed it. Vulnerability research has found plenty of genuine implementation flaws as well, with commercial and open-source stacks falling repeatedly at industrial control hacking competitions and a sustained research effort in 2021 and 2022 producing vulnerabilities across several widely used stacks and gateways. Those matter, but they are a smaller problem than endpoints that require no authentication at all.

Hardening Checklist

  1. Disable the None policy entirely. If a client cannot do better, that is a procurement finding, not a configuration decision.
  2. Require SignAndEncrypt, not Sign alone, on any channel crossing a zone boundary.
  3. Turn off anonymous access and give each client application and each human user its own identity, with node-level permissions rather than blanket read and write.
  4. Operate the trust lists. Decide who issues application certificates, how long they live, how they are renewed, and how a compromised one is rejected. For anything beyond a handful of applications, run a Global Discovery Server rather than copying files between machines.
  5. Restrict discovery. The discovery endpoint enumerates available endpoints and their security settings, which is useful to an integrator and equally useful to an attacker; limit who can reach it.
  6. Place the server deliberately. An OPC UA server serving business consumers belongs in the industrial demilitarised zone, with a separate server inside the control zone, mirroring the pattern used for the historian. Reverse connect, where the server initiates the connection outward, avoids opening an inbound path at all.
  7. Patch the stack. OPC UA implementations are software libraries with their own advisories, and the version embedded in a controller is often years behind the vendor’s current release.
  8. Monitor the audit events and forward them to the same place as everything else, since certificate rejections and unexpected session creation are high-quality signals.

Where It Is Going

OPC UA over time-sensitive networking, marketed as OPC UA FX, extends the standard down to controller-to-controller communication at the field level, which is the part of the stack that Modbus and PROFINET still occupy. The security model comes with it, which over a long replacement cycle is the most significant improvement available to industrial networks. In the meantime, treating OPC UA as the preferred conduit protocol between zones, configured properly, is one of the better architectural decisions available under IEC 62443.

At Privia Security, we review OPC UA deployments and their certificate handling through our Infrastructure and Architecture Review Services.

FAQ – Frequently Asked Questions

Is OPC UA Secure by Default?

It is secure by capability, not by default. The specification includes certificate-based application authentication, signing, encryption, user tokens, and audit events, but a server can be configured with security policy None and anonymous access, and many are, because certificate handling is awkward during commissioning. The first question in any assessment is which endpoints are offered and with which policies.

What Is the Difference Between Sign and SignAndEncrypt?

Sign applies a message signature, giving integrity and authenticity but leaving the content readable to anyone capturing traffic. SignAndEncrypt adds confidentiality. For traffic crossing a zone boundary, or anything carrying credentials, recipes, or commercially sensitive process data, SignAndEncrypt is the correct setting; Sign alone is acceptable only inside a well-controlled network segment.

Should We Migrate From OPC Classic to OPC UA?

Where the equipment supports it, yes. OPC Classic depends on DCOM, which Microsoft has progressively hardened to the point of breaking many legacy configurations, requires wide dynamic port ranges that make firewalling impractical, and relies on Windows domain trust spanning a security boundary. OPC UA authenticates with certificates, encrypts, and traverses a firewall on a single port.

What Is a Global Discovery Server?

A component that acts as certificate authority and registry for an OPC UA installation, issuing application instance certificates, distributing trust lists, and handling renewal and revocation. Manually copying certificates between machines is workable for a handful of applications and unmanageable beyond that, so a discovery server is what makes proper security practical at plant scale.

Related Terms

You May Be Interested In These

What Is Root and Jailbreak Detection?

Cybersecurity Terms

17 November 2026

What Is Root and Jailbreak Detection?

Read More
What Is Detection Engineering?

Cybersecurity Terms

17 November 2026

What Is Detection Engineering?

Read More