Client-Side Cryptographic Key Management for Secure User Sessions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for securing user information are inadequate as they rely on encryption/decryption keys stored on servers, making them vulnerable to hacking and data breaches when server access is compromised.
Innovation Solution
A method where the application manager computing device obtains and uses a unique per-client one-time use cryptographic key for encrypting or decrypting user information, deleting the key after the user session is completed to enhance security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If encryption/decryption keys are stored on the server to secure user information, then user information can be encrypted and decrypted, but the system becomes vulnerable to hacking and data breaches when server access is compromised
Solution Approach 1:
The patent extracts the cryptographic key from the server storage and relocates it to the client computing device. The server no longer stores the key, instead it only stores encrypted user information. The client device stores the key locally and uses it to encrypt/decrypt information, thereby removing the harmful vulnerability of server-based key storage while maintaining the security function.
Solution Approach 2:
The patent inverts the conventional approach by switching from server-based key storage to client-based key storage. Instead of the server holding the key to protect user information, the client device holds the key and the server only handles encrypted data. This inversion eliminates the risk of key exposure through server hacking.
2Device complexity
If a single encryption key is used for all users on the server, then key management is simplified, but security is reduced as a compromised key exposes all user information
Solution Approach 1:
The patent segments the single encryption key into multiple user-specific keys, with each client device storing its own unique key. This segmentation ensures that if one key is compromised, only that specific user's information is exposed, not all user information. The complexity is managed at the client level rather than the server level.
Solution Approach 2:
The patent applies local quality by assigning each client device its own unique cryptographic key stored locally on the device. Each key has different properties (uniqueness and local storage) tailored to its specific client, rather than using a uniform shared key. This provides security customization for each user while keeping management simple.
3Device complexity
If the cryptographic key is stored in the same location as encrypted user information, then storage is simplified, but security is compromised as both are accessible through the same access point
Solution Approach 1:
The patent extracts the cryptographic key from the server's storage location and relocates it to the client device. This physical separation of the key and encrypted information eliminates the risk that a single access point compromise would expose both the key and the data, while maintaining simplified storage through local client storage.
Data Source
AI summary
A method, non-transitory computer readable medium and application manager computing device comprises obtaining at least one cryptographic key from a request by a client computing device for a user session. User information corresponding to a user is encrypted or decrypted using the cryptographic key. The request is authenticated based on encryption or decryption of the user information. The cryptographic key is deleted after the completion or termination of the user session.