Cross-Domain Microservice Security via Gateway Mediation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In distributed systems, particularly in modern vehicles and other applications, there is a challenge in securely sharing insights generated by sensors across different domains, where security and authorization vary significantly.
Innovation Solution
The method involves registering an application with an anchor in the first domain, obtaining signed tokens for synthetic sensors in a second domain, and using these tokens to request and receive insights securely, while synchronizing permissions tables and using gateways or bridges for authorization and communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If insights are shared across domains with different security levels, then the versatility and utility of sensor data is improved, but the security and confidentiality of proprietary algorithms and machine learning code deteriorates
Solution Approach 1:
The patent introduces a gateway as an intermediary component that mediates between domains with different security levels. The gateway receives insights from synthetic sensors in one domain, verifies authorization tokens, and selectively forwards insights to applications in other domains. This intermediary architecture enables cross-domain sharing while maintaining security boundaries, as the gateway controls and filters the flow of sensitive information based on authorization credentials.
Solution Approach 2:
The system segments the distributed system into distinct domains with different security levels, each domain having its own trust anchor and security policies. Insights are segmented and selectively shared only with authorized applications in specific domains, rather than universally distributing all data. This segmentation allows proprietary algorithms to remain protected within their home domain while still enabling controlled sharing with external applications.
2Reliability
If a centralized permission management system is implemented, then the reliability of authorization control is improved, but the device complexity and infrastructure requirements worsen
Solution Approach 1:
The patent moves permission management from a centralized cloud-based system to a distributed architecture where each domain has its own trust anchor operating in a different dimension (local domain level). Applications present authorization tokens that are verified by gateways within the same domain or by trusted gateways in other domains. This dimensional shift from centralized to distributed permission management maintains reliability through cryptographic verification while reducing infrastructure complexity by eliminating the need for a single centralized permission server.
3Reliability
If cryptographic verification is performed for every insight request, then data integrity and confidentiality are improved, but the processing time and computational overhead worsen
Solution Approach 1:
The system performs preliminary cryptographic action by issuing authorization tokens in advance to applications before they need to access insights. These tokens contain pre-verified authorization credentials that allow applications to prove their identity and permissions without requiring real-time cryptographic verification for each individual insight request. The heavy cryptographic lifting is done beforehand during token issuance, while subsequent insight access uses the pre-established credentials for faster verification.
Data Source
AI summary
A method at a network element for securely sharing services across domains, the method including receiving a request at the network element to add a first domain and an edge domain to a system; provisioning a public key of the network element to the first domain and the edge domain; receiving a public key of the first domain; populating, in the network element, a table with services provided by the first domain or the edge domain; populating, in the network element, a second table with applications installed at the first domain or edge domain and permissions for services for the applications; and controlling access to the services by the applications.