Cloud On-Premise Tunnel Management via Dynamic Passport Tokens
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current cloud, mobile, and web-based applications fail to provide secure, highly available, bi-directional connections to on-premise networks, lacking fine-grained access control and scalability, and require complex manual setup of credentials and DMZ port openings, which are challenging and insecure.
Innovation Solution
A method using a 'passport service' that creates a passport on a cloud application with connectivity details, generates a dynamically generated passport token, and binds the cloud application with an on-premise appliance to establish secure tunnels without requiring DMZ port openings, using a connectivity library to simplify cloud connectivity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If virtual private network based solutions are used for cloud to on-premise connections, then connection establishment is simplified, but fine-grained access control and scalability are not provided
Solution Approach 1:
The patent segments the connection management into discrete passport tokens, each representing a specific access credential with defined connectivity properties. Instead of treating connections as monolithic VPN tunnels, the system divides access control into granular token units that can be individually managed, bound to specific applications, and revoked independently, enabling fine-grained access control while maintaining ease of connection establishment.
Solution Approach 2:
The patent implements dynamic passport token generation and binding mechanisms that adapt to different cloud applications and on-premise resources. The system dynamically creates passport tokens with specific connectivity properties, binds them to particular applications, and manages their lifecycle automatically, providing both ease of operation and adaptability through dynamic rather than static connection management.
2Reliability
If manual setup of credentials and DMZ port openings is performed, then secure access is achieved, but development complexity and configuration time increase
Solution Approach 1:
The patent implements self-service mechanisms where the passport service automatically generates passport tokens, manages their lifecycle, and handles binding to cloud applications without requiring manual DMZ port configuration or credential setup. The system autonomously manages the security credentials and connection parameters, reducing configuration complexity while maintaining secure access through automated security policies and token-based authentication.
Solution Approach 2:
The patent introduces a passport service as an intermediary between cloud applications and on-premise resources, which mediates the authentication and connection establishment processes. This intermediary automatically manages credentials and generates passport tokens, eliminating the need for manual DMZ port openings and complex credential setup while ensuring secure access through centralized security management.
3Adaptability or versatility
If DMZ port opening is required for cloud connections, then network accessibility is improved, but security risks and organizational feasibility decrease
Solution Approach 1:
The patent extracts the security vulnerability of DMZ port opening by replacing it with a token-based authentication system. Instead of requiring open network ports that expose the on-premise network to potential attacks, the system uses passport tokens that provide authenticated access without requiring DMZ infrastructure, thereby maintaining network accessibility while eliminating the security risks associated with DMZ port openings.
Solution Approach 2:
The patent uses short-lived passport tokens as disposable credentials that provide temporary, limited-access authentication. These tokens are generated on-demand, used for specific connection purposes, and then revoked or expire automatically. This approach provides the necessary network accessibility for cloud connections while minimizing security risks through ephemeral, purpose-limited credentials rather than permanent open ports.
4Reliability
If multiple systems require credential setup for cloud integration, then access control is established, but development and testing complexity increase
Solution Approach 1:
The patent implements a universal passport token system that can be used across multiple cloud applications and on-premise resources. Instead of requiring separate credential setups for each system integration, the passport service generates universal tokens that work across different applications and resources, maintaining access control while significantly reducing development and testing time by eliminating redundant credential configuration for each system.
Data Source
AI summary
The described herein relates to a method executed by a passport service executed by at least one processor coupled to at least one memory. The method includes creating a passport on a cloud application that comprises connectivity details for a tunnel and activating an on-premise appliance of an on-premise system by delivering the passport to the on-premise appliance to build the tunnel. The method further includes generating a passport token via the passport, wherein the passport token comprises dynamically generated connectivity properties. The method also includes binding the cloud application and the on-premise appliance based on the dynamically generated connectivity properties of the passport token and the connectivity details of the passport.


