Search

16 result(s) for Authorization

• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  3.1.13 Authorization
  Authorization ability to grant access to a system resource Note 1 to entry:  Authorization of access to resources should be based on the need-to-know principle. It is important
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  3.1.18 Claim
  Claim statement in an AccessToken that asserts information about the subject which the Authorization Service knows to be true Note 1 to entry: Claims can include username, email, and Roles
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  3.1.43 SecurityKeyService
  SecurityKeyService Server that accepts AccessTokens issued by the Authorization Service and returns security keys that can be used to access the specified Resource Note 1 to entry: The keys
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.2.3 Authorization
  Authorization The access to read, write, or execute resources should be authorized for only those entities that have a need for that access within the requirements of the system. Authorization ... system depends in part on the functionality supported by the Server , but in general Authorization should be given based on the need-to-know principle i.e. a user should
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.2.4 Confidentiality
  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
  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 of this
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.3.4 Message spoofing
  perform unauthorized operations and avoid 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.6 Message replay
  attacker could attempt to establish a Session using a recorded Session . Message replay impacts Authorization and during Session / SecureChannel establishment Authentication. See 5.1.6 for the reconciliation of this threat
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.3.13 Compromising user credentials
  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
  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 of this threat
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.3.17 Downgrade Attack
  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 of this threat
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.5.2.2 Session application layer
  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 are managed
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  5.2.4 Authorization
  Authorization Authorization could be provided via Roles ( 4.12 ) and supplied by a Authorization Server in a GDS. In an environment of mixed vendor products, the GDS can provide a consistent ... Authorization management. OPC UA Applications that are part of a larger industrial automation product can manage Authorizations consistent with the Authorization management of that product. Identification and Authentication of users
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  6.18 Zero trust environments
  provide both application level and user level authentication, and support for central management of Authorization and Authentication (GDS functionality), are all concepts desired in a zero-trust environment. Another
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.1.5 Creating a Session
  provider depends on the user identity token. It could be a Certificate Authority , an Authorization Service or a proprietary database of some sort. The Client and Server shall prove possession
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  7.4.2 Session-less Services
  less Services (see OPC 10000-4 ) may be invoked via HTTPS POST. The HTTP Authorization header is used to specify the UserIdentity used to determine what permissions are available ... caller. The Authorization header may specify a Basic token with a UserName/Password or a Bearer token (see IETF RFC 6750 ) with an AccessToken provided by an AuthorizationService . The HTTP Accept