Search

26 result(s) for Authentication

• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  3.1.12 Authentication
  Authentication process that assures that the identity of an entity such as a Client , Server , Publisher or user can be verified
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  3.1.6 Asymmetric Cryptography
  Signature algorithm when an entity "A" requires message Integrity or to provide Authentication for data sent to entity "B", entity A uses its Private
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.2.2 Authentication
  Authentication Entities such as Clients , Servers , and users should prove their identities. Authentication can be based on something the entity is, has, or knows
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.2.4 Confidentiality
  Confidentiality, data encryption algorithms using special secrets for securing data are used along with Authentication and Authorization mechanisms for accessing that secret
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.3.3 Eavesdropping
  compromised operating system. Eavesdropping impacts Confidentiality directly and if session establishment is not secured Authentication and Authorization . It also indirectly threatens all other security objectives. See 5.1.3 for the reconciliation
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.3.4 Message spoofing
  detection of their activities. Message spoofing impacts Integrity , Authorization and during session / SecureChannel establishment Authentication . See 5.1.4 for the reconciliation of this threat
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.3.5 Message alteration
  system. Message alteration impacts Integrity, Authorization, Auditability, Non-Repudiation and during session / SecureChannel establishment Authentication . See 5.1.5 for the reconciliation of this threat
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.3.13 Compromising user credentials
  compromised credentials are used, subsequent activities could all appear legitimate. Compromised user credentials impact Authentication , Authorization and Confidentiality . See 5.1.12 for the reconciliation of this threat
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.3.14 Compromising identity services
  used and or granted any roles or rights. Compromised identity services directly impact Authentication and Authorization , but it can indirectly impact all security objectives. See 5.1.12 for the reconciliation
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.3.17 Downgrade Attack
  Discovery response to remove security options from the available endpoints. Message suppression directly impacts Authentication and Authorization , but it can indirectly impact all security objectives. See 5.1.15 for the reconciliation
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.5.2.2 Session application layer
  Session in the Application Layer. The Application Layer also manages the security objectives user Authentication and user Authorization (see 4.11 for more detail on user authorization). The security objectives that
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.5.2.3 Session communication layer
  communication layer The Communication Layer provides security mechanisms to meet Confidentiality , Integrity and application Authentication as security objectives. In some cases, it also meets the Perfect Forward Secrecy security objective ... maintain Confidentiality , Message Signature s to maintain Integrity and Certificates to provide application Authentication. In addition, the SecureChannel provides Perfect Forward Secrecy when the SecureChannel is used with Elliptic Curve
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.5.2.4 Transport layer
  same shared certificate have the same settings. HTTPS does not require application Authentication , if this is required it can be included as part of Session establishment
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.5.2.5 Session-less Service invocation
  overview and see OPC 10000-6 for details). The session-less communication provides User Authentication via an Access Token. The communication channel provides Confidentiality and Integrity. The communication channel could ... such as HTTPS , which relies on transport protocols to provide security. In addition, User Authentication and/or Application Authentication can also be established by the use of an AccessToken which
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.5.3.2 Broker-less
  makes use of the standard Client / Server security described in 4.5.2 to establish application Authentication as well as user Authentication . This approach allows all applications ( Publishers and/or Subscribers
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.5.3.3 Broker
  Broker interactions can provide security mechanisms to meet Confidentiality , Integrity and application or user Authentication as security objectives. If the published message is not secured using the shared SymmetricKey concepts
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.9 User Authentication
  User Authentication User Authentication is achieved when the Client passes user credentials to the Server as specified via Session Services (described in OPC 10000-4 ). The Server can authenticate ... changed using the ActivateSession Service in order to meet needs of the application. User Authentication is not directly part of the Publish - Subscribe communication pattern but is used as part
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.10 Application Authentication
  Application Authentication OPC UA uses a concept conveying Application Authentication to allow applications that intend to communicate to identify each other. Each OPC UA ApplicationInstance has a Certificate ( ApplicationInstanceCertificate ) assigned ... HTTPS can be used to create SecureChannels , however, these channels do not provide Application Authentication . If Authentication is required, it is based on user credentials (User Authentication see 4.9 ). More
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.12 Roles
  granted Roles based on connection information ( Session creation). Roles could be restricted by User Authentication , Application Authentication , SecurityModes , or Transports . The assignment of Roles and AccessRestrictions is application specific
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  5.1.2.2 Message flooding
  their product documentation as specified in OPC 10000-7 . OPC UA user and Client Authentication reduce the risk of a legitimate Client being used to mount a flooding attack ... reconciliation of Authentication in 5.2.3 . The Client protects itself from floods by have a max message size limit, automatically closing connections where the limit is exceeded. The Clients also ignore
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  5.1.2.3 Resource exhaustion
  Resource exhaustion OPC UA user and Client Authentication reduce the risk of a legitimate Client being used to mount a resource exhaustion attack. Additionally, Server Auditing allows the detection
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  5.2.2 Application Authentication
  Application Authentication OPC UA Applications support Authentication of the entities with which they are communicating. As specified in the GetEndpoints and OpenSecureChannel services in OPC 10000-4 , OPC UA Client ... required to obtain the shared keys from a SecurityKeyService (SKS). Although the application authentication is not directly between the Subscriber and the Publisher, the SKS ensures that only authenticated applications
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  5.2.3 User Authentication
  User Authentication OPC UA Applications support Authentication of users by providing the necessary Authentication credentials to the other entities. As described in the ActivateSession service ... argument in its subsequent ActivateSession call. For session-less services User Authentication can be accomplished using an AccessToken which is obtained from an AuthorizationService (see OPC 10000-6 for details
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  5.2.4 Authorization
  product can manage Authorizations consistent with the Authorization management of that product. Identification and Authentication of users is specified in OPC UA so that Client and Server applications can recognize ... Servers respond with the Bad _ UserAccessDenied error code to indicate an Authorization or Authentication error as specified in the status codes defined in OPC 10000-4 . In PubSub interactions user
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  6.18 Zero trust environments
  down to individual Nodes , the ability to provide both application level and user level authentication, and support for central management of Authorization and Authentication (GDS functionality), are all concepts desired
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  13.2.1 Locating Server via GDS
  resolved locally. The Session established by the ConnectionManager shall support the use of authentication and/or encryption. This includes: Application Authentication based on security mode and policy The use of Roles ... this may require user authentication or specific ApplicationInstance certificates) If SecurityPolicyUri contains an empty or null string, the EndpointDescription on the Server with the highest SecurityLevel of the ones supported