PD CLC/TR 62541-2:2010
Withdrawn
A Withdrawn Standard is one, which is removed from sale, and its unique number can no longer be used. The Standard can be withdrawn and not replaced, or it can be withdrawn and replaced by a Standard with a different number.
View Superseded by
OPC unified architecture Security model
Hardcopy , PDF
29-12-2021
English
31-10-2010
INTRODUCTION
1 Scope
2 Normative references
3 Terms, definitions, abbreviations and conventions
4 OPC UA Security architecture
5 Security reconciliation
6 Implementation considerations
Bibliography
Annex ZA (normative) - Normative references to
international publications with
their corresponding European publications
Gives the OPC Unified Architecture (OPC UA) security model. This provides the security threats of the physical, hardware and software environments in which OPC UA is expected to run. Also provides how OPC UA relies upon other standards for security. Describes an overview of the security features that are specified in other parts of the OPC UA specification.
Committee |
GEL/65/3
|
DevelopmentNote |
Supersedes 08/30187449 DC. (11/2010)
|
DocumentType |
Standard
|
Pages |
36
|
PublisherName |
British Standards Institution
|
Status |
Withdrawn
|
SupersededBy | |
Supersedes |
This part of IEC 62541 describes the OPC Unified Architecture (OPC UA) security model. It describes the security threats of the physical, hardware and software environments in which OPC UA is expected to run. It describes how OPC UA relies upon other standards for security. It gives an overview of the security features that are specified in other parts of the OPC UA specification. It references services, mappings, and profiles that are specified normatively in other parts of this series of standards.
Note that there are many different aspects of security that have to be addressed when developing applications. However since OPC UA specifies a communication protocol, the focus is on securing the data exchanged between applications.
This does not mean that an application developer can ignore the other aspects of security like protecting persistent data against tampering. It is important that the developer look into all aspects of security and decide how they can be addressed in the application.
This part of IEC 62541 is directed to readers who will develop OPC UA client or server applications or implement the OPC UA services layer.
It is assumed that the reader is familiar with Web Services and XML/SOAP. Information on these technologies can be found in SOAP Part 1 and SOAP Part 2.
Standards | Relationship |
IEC TR 62541-2:2010 | Identical |
CLC/TR 62541-2:2010 | Identical |
IEC 62541-4:2015 | OPC Unified Architecture - Part 4: Services |
IEC 62541-7:2015 | OPC unified architecture - Part 7: Profiles |
IEC TR 62541-2:2016 | OPC unified architecture - Part 2: Security Model |
IEC 62541-3:2015 | OPC unified architecture - Part 3: Address Space Model |
CLC/TR 62541-1:2010 | OPC unified architecture - Part 1: Overview and concepts |
IEC TR 62541-1:2016 | OPC unified architecture - Part 1: Overview and concepts |
IEC 62541-5:2015 | OPC Unified Architecture - Part 5: Information Model |
IEC 62541-6:2015 | OPC unified architecture - Part 6: Mappings |
Access your standards online with a subscription
Features
-
Simple online access to standards, technical information and regulations.
-
Critical updates of standards and customisable alerts and notifications.
-
Multi-user online standards collection: secure, flexible and cost effective.