Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
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.

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.
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.
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.
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.
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.
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.
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.
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.
You May Be Interested In These
Cybersecurity Terms
17 November 2026
What Is the Difference Between Nessus and Tenable.io?
Read MoreWe use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.