Security Token Service Cross-Layer Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Industrial control systems face challenges in secure communication across security layers due to the lack of domain trust between levels, leading to increased development and maintenance time, and costs associated with replicating data and software across domains, which does not meet security and legal requirements.
Innovation Solution
The implementation of a security layer in industrial control systems that includes a user database, web server, secure token server (STS), and application server to authenticate operators and negotiate access across security layers using tokens, leveraging open standards like OpenIDConnect and OAuth2.0 to translate user identities into tokens for authorization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If domain trust is established between security layers, then secure communication across layers is enabled, but system complexity and authentication overhead increase
Solution Approach 1:
The patent introduces a Security Token Service (STS) as an intermediary component that mediates authentication between different security layers. The STS issues security tokens that contain user identity and authorization information, allowing cross-layer communication without requiring direct trust relationships between all domain controllers. This intermediary mechanism enables secure communication while centralizing authentication logic to manage complexity.
Solution Approach 2:
The patent transforms the authentication mechanism by changing from direct domain controller verification to token-based authentication. Security tokens encode user credentials and authorization levels, allowing the system to verify identity through token validation rather than complex inter-domain trust relationships. This parameter change simplifies the authentication process while maintaining security across layers.
2Adaptability or versatility
If data and software are replicated across security domains, then access to resources is enabled, but development time, maintenance time, and costs increase
Solution Approach 1:
The patent uses security tokens as lightweight copies of user identity and authorization information rather than replicating entire user databases or software across domains. The token contains essential credentials that can be validated without accessing the original user database, enabling resource access while avoiding the overhead of full data replication.
Solution Approach 2:
The Security Token Service provides a universal authentication mechanism that works across multiple security layers and domains. A single token issuance system serves all cross-layer authentication needs, eliminating the need for separate replication and synchronization mechanisms for each domain pair. This multi-functional approach reduces development and maintenance overhead.
3Ease of operation
If users are permitted to cross security layers, then operational flexibility is improved, but security risks and attack surface increase
Solution Approach 1:
The patent implements role-based access control where security tokens encode specific authorization levels and permitted actions for each user. Instead of allowing universal cross-layer access, each token contains localized permissions tailored to the user's role and the specific resources they need to access. This ensures operational flexibility while limiting exposure to security risks by restricting access to only what is necessary.
Solution Approach 2:
The authentication system dynamically adjusts access permissions based on the user's identity, role, and the specific resource being accessed. Security tokens are issued with time-limited validity and scope-specific permissions, allowing the system to provide operational flexibility when needed while automatically revoking or limiting access when not required. This dynamic approach balances flexibility with security risk mitigation.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A security layer (202) in an industrial control and automation system (100) includes a user database (214), a web server (208), a secure token server (STS) (210), and an application server (212). The user database is configured to store identities of users with credentials to access controls of the security layer. The web server is configured to identify (505) an operator using a client device (206). The STS is configured to authenticate (510) the operator for the security layer. The application server is configured to negotiate (520) access for the client device for a target application server (220) in a target security layer (204).