Check: OPC UA communication and security

Knowledge check · self-test
Check: OPC UA communication and security
Check communication patterns and security-policy selection.
Check communication patterns and security-policy selection.
Checkpoint: Communication Pattern {.depth-l0}
You now know:
- Client-server fits direct browse, read, write, call, subscription, SCADA, HMI, and configuration workflows.
- PubSub fits decoupled telemetry over MQTT or AMQP when cloud analytics should not maintain direct sessions to machines.
- A 500-machine factory often needs both: operational client-server locally, aggregated PubSub through edge gateways for cloud consumers.
:::
::: {.callout-tip}
##
Checkpoint: Security Baseline {.depth-l0}
You now know:
- Security Policy None is for isolated testing, not production.
- Basic256Sha256 is a common supported baseline; Aes256-Sha256-RsaPss is the stronger target when endpoints and timing support it.
- Release evidence needs application certificates, user identity, trust-list ownership, authorization roles, and audit logging, not only encryption enabled.
:::
Back to OPC UA: Architecture, Models, and Security: Establish Identity and Permission