Which Security Modes does an OPC UA SecureChannel support per the standard?
C — None, Sign and SignAndEncrypt
The OPC UA specification defines exactly three Security Modes on a SecureChannel: None (no protection, dev/test only), Sign (authentication and integrity via HMAC, no confidentiality), and SignAndEncrypt (sign plus AES encryption). Option A is wrong because "Encrypt" without signing is not a defined mode; you cannot encrypt without also signing in OPC UA. Option B is wrong because it omits the mandatory SignAndEncrypt mode used in production. Option D is wrong because it removes the None mode, which is legally part of the standard even though it is unsuitable for production. In production you should always choose SignAndEncrypt with a strong Security Policy such as Basic256Sha256, Aes128_Sha256_RsaOaep or Aes256_Sha256_RsaPss.
Treat SecurityMode=None as a red flag in any production audit: it is acceptable only on a strictly isolated commissioning network, never on a routed plant network.
- A.None and Encrypt
- B.None and Sign
- C.None, Sign and SignAndEncrypt✓
- D.Sign and SignAndEncrypt only
OPC UA bank in preparation
The full OPC UA bank isn't available yet. Drop your email to get notified at launch and grab an early-bird discount.
Join the waitlist →See the 9 other OPC UA practice questions
Related questions
- What is the complete format of an OPC UA NodeId?2. NodeIds · NodeId-Format
- An OPC UA Subscription groups several MonitoredItems and publishes value changes periodically (PublishingInterval typically 100-1000 ms); the server keeps a buffer of unacknowledged notifications for reliability.3. Services · Subscriptions
- OPC UA uses X.509 certificates to authenticate applications (both client and server): each application holds its own certificate, and trust is established mutually through the exchange that happens during the SecureChannel handshake.4. Security · Zertifikate
- OPC UA Pub/Sub supports several transports: UDP multicast (lowest latency, machine-to-machine), MQTT (cloud-friendly via broker) and AMQP (enterprise messaging), making it adaptable to a wide range of use cases.9. Pub/Sub · Transport-Optionen
- OPC UA Pub/Sub supports two encodings: Binary (compact and fast, about 30% of the payload size of JSON) and JSON (human-readable, debug-friendly, easy to integrate with web and REST stacks). The choice depends on the performance versus interoperability trade-off.9. Pub/Sub · JSON- vs. Binär-Encoding