IEC 62541-7:2025
OPC unified architecture - Part 7: Profiles
IEC 62541-7: 2025 specifies value and structure of Profiles in the OPC Unified Architecture.OPC UA Profiles are used to segregate features with regard to testing of OPC UA products and the nature of the testing. The scope of this document includes defining functionality that can only be tested. The definition of actual TestCases is not within the scope of this document, but the general categories of TestCases are covered by this document.Most OPC UA applications will conform to several, but not all of the Profiles.This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.This edition includes the following significant technical changes with respect to the previous edition:a) Profiles and ConformanceUnits are not part of this document, but are solely managed in a public database as described in Clause 1.
IEC 62541-7: 2025 specifies value and structure of Profiles in the OPC Unified Architecture.
OPC UA Profiles are used to segregate features with regard to testing of OPC UA products and the nature of the testing. The scope of this document includes defining functionality that can only be tested. The definition of actual TestCases is not within the scope of this document, but the general categories of TestCases are covered by this document.
Most OPC UA applications will conform to several, but not all of the Profiles.
This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) Profiles and ConformanceUnits are not part of this document, but are solely managed in a public database as described in Clause 1.
IEC 62541-7:2020 defines the OPC Unified Architecture (OPC UA) Profiles. The Profiles in this document are used to segregate features with regard to testing of OPC UA products and the nature of the testing (tool based or lab based). This includes the testing performed by the OPC Foundation provided OPC UA CTT (a self-test tool) and by the OPC Foundation provided Independent certification test labs. This could equally as well refer to test tools provided by another organization or a test lab provided by another organization. What is important is the concept of automated tool-based testing versus lab-based testing. The scope of this standard includes defining functionality that can only be tested in a lab and defining the grouping of functionality that is to be used when testing OPC UA products either in a lab or using automated tools. The definition of actual TestCases is not within the scope of this document, but the general categories of TestCases are within the scope of this document. Most OPC UA applications will conform to several, but not all, of the Profiles. This third edition cancels and replaces the second edition published in 2015. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a) new functional Profiles: • profiles for global discovery and global certificate management; • profiles for global KeyCredential management and global access token management; • facet for durable subscriptions; • standard UA Client Profile; • profiles for administration of user roles and permissions. b) new transport Profiles: • HTTPS with JSON encoding; • secure WebSockets (WSS) with binary or JSON encoding; • reverse connectivity. c) new security Profiles: • transportSecurity – TLS 1.2 with PFS (with perfect forward secrecy); • securityPolicy [A] – Aes128-Sha256-RsaOaep (replaces Base128Rsa15); • securityPolicy – Aes256-Sha256-RsaPss adds perfect forward secrecy for UA TCP); • user Token JWT (Jason Web Token). d) deprecated Security Profiles (due to broken algorithms): • securityPolicy – Basic128Rsa15 (broken algorithm Sha1); • securityPolicy – Basic256 (broken algorithm Sha1); • transportSecurity – TLS 1.0 (broken algorithm RC4); • transportSecurity – TLS 1.1 (broken algorithm RC4). e) deprecated Transport (missing support on most platforms): • SOAP/HTTP with WS-SecureConversation (all encodings).
The Requirements department helps you quickly locate within the normative text:
- mandatory clauses to satisfy,
- non-essential but useful clauses to know, such as permissions and recommendations.
The identification of these types of clauses is based on the document “ISO / IEC Directives, Part 2 - Principles and rules of structure and drafting of ISO documents ”as well as on a constantly enriched list of verbal forms.
With Requirements, quickly access the main part of the normative text!

COBAZ is the simple and effective solution to meet the normative needs related to your activity, in France and abroad.
Available by subscription, CObaz is THE modular solution to compose according to your needs today and tomorrow. Quickly discover CObaz!
Request your free, no-obligation live demo
I discover COBAZ