← Resources·Protocols Guide

OPC UA security configuration — a step-by-step guide

OPC UA is the rare industrial protocol with real security built in — signing, encryption, certificates, and user authentication are all in the specification. Which makes the common field configuration all the more frustrating: security mode None, anonymous login, and a trust list containing everything that ever asked. This guide covers what the settings mean and the order to fix them in.

8 min read
·
For controls and OT engineers
·
Pro guide
The model

Three layers, configured separately

OPC UA security is not one switch. Transport protection, application identity, and user identity are independent layers — and a deployment is only as strong as the weakest one you left at its default.

TRANSPORT SECURITY
Signing and encryption of every message between client and server, negotiated per connection. This is the layer the security mode and security policy settings control — and the one most often switched off.
APPLICATION AUTHENTICATION
Every OPC UA application holds an X.509 certificate. Client and server exchange and validate certificates before a session opens — each side only talks to applications in its trust list.
USER AUTHENTICATION & AUTHORISATION
Separate from the application layer: the session carries a user identity — anonymous, username/password, or a user certificate — which the server maps to read/write permissions on its address space.
Pro members only
The full guide is part of Control Signal Pro

Pro members get every deep-dive guide, plus the dashboard, asset register, and CVE alerts matched to the equipment they actually run. Sign in to upgrade, or start with a free account.

Sign in to upgradeCreate free account
Related guides
Guide
Modbus Security
Securing the protocol that has no security of its own
Guide
OT Network Segmentation
Zones, conduits, and the Purdue model in practice