Difference between revisions of "uaCap:Transport uatcp secure"

From UaCapabilities
Jump to: navigation, search
Line 13: Line 13:
 
{{uaConformance|
 
{{uaConformance|
 
* [http://opcfoundation.org/UA-Profile/Transport/uatcp-uasc-uabinary  '''UA TCP Transport Profile''']
 
* [http://opcfoundation.org/UA-Profile/Transport/uatcp-uasc-uabinary  '''UA TCP Transport Profile''']
* [http://opcfoundation.org/UA/SecurityPolicy#... '''UA Security Profile''']
+
* [http://opcfoundation.org/UA/SecurityPolicy#Basic256Sha256 '''One or more UA Security Profiles''']
 
|
 
|
 
* [http://opcfoundation.org/UA-Profile/Transport/uatcp-uasc-uabinary  '''UA TCP Transport Profile''']
 
* [http://opcfoundation.org/UA-Profile/Transport/uatcp-uasc-uabinary  '''UA TCP Transport Profile''']
* [http://opcfoundation.org/UA/SecurityPolicy#... '''UA Security Profile''']
+
* [http://opcfoundation.org/UA/SecurityPolicy#Basic256Sha256 '''One or more UA Security Profiles''']
 
}}
 
}}

Revision as of 13:19, 5 February 2015

URN:          https://opcfoundation.org/wiki/index.php/Transport/UA_TCP/Secured

Description
This transport capability supplements the UA_TCP transport with security, including:

  • Authentication of communication partner based on digital certificates that are exchanged during the establishment of a secure channel. This is based on Public Key Infrastructure (PKI) standards.
  • Efficient Data encryption algorithms to provide Confidentiality
  • Efficient Message signatures to provide Integrity

Usage Considerations

  • Application authentication allows restricting access to trusted parties.
  • End-to-end encryption offers uninterrupted protection of data between Client and Server resulting in a higher degree of security than transport protocols that protect messages by establishing secure connection between two hosts (HTTPS, for example).
  • Can be applied to a wide range of devices and application, from control and field devices that require security to enterprise level applications.

Conformance Testing

Client Server