Per-Record Key Agreement for Cloud Secrets Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud platforms using a single encryption key for data storage are vulnerable to compromise, risking unauthorized disclosure and potential harm to users and organizations, as the breach of a single key can expose all data.
Innovation Solution
Implementing a secrets management system that generates a new key pair for each data record, using key agreement protocols like Elliptic Curve Diffie-Hellman to derive a shared secret and encryption key, ensuring each record is encrypted with a unique key, and erasing the private key after use to prevent reuse and enhance security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If a single encryption key is used to encrypt all data in a data store, then the encryption process is simple and efficient, but the entire data store becomes vulnerable to compromise if that key is breached
Solution Approach 1:
The patent divides the data store into multiple segments or records, each encrypted with a separate encryption key. Instead of using one master key for all data, the system generates unique encryption keys for individual records or data segments, so that compromise of one key does not expose the entire data store. This segmentation approach maintains security while managing complexity through systematic key generation and management.
2Reliability
If a unique encryption key is generated for each data record, then data security is significantly improved, but the complexity of key management increases
Solution Approach 1:
The patent introduces a key management service or intermediary component that automatically handles the generation, distribution, and management of encryption keys. This intermediary service reduces the burden on individual applications or users by centralizing key management functions, thereby maintaining high security through unique per-record keys while reducing the perceived complexity for end users.
Solution Approach 2:
The system implements automated key generation and management mechanisms where encryption keys are automatically created and assigned to data records without requiring manual intervention. The key management infrastructure operates autonomously to handle key lifecycle events, reducing operational complexity while maintaining security requirements.
3Ease of operation
If cryptographic keys are stored securely on a server, then centralized key management is achieved, but the server becomes a single point of failure and potential compromise
Solution Approach 1:
The patent distributes key storage across multiple locations or uses a hierarchical key structure where master keys are segmented and distributed. Instead of storing all keys in a single centralized location that could be compromised, the system divides key management into distributed components or uses key hierarchies where compromise of one component does not expose all keys.
Solution Approach 2:
The patent extracts sensitive key material from centralized storage and distributes it to clients or edge devices. By taking key management out of the centralized server and distributing key responsibilities to multiple entities, the system reduces the single point of failure risk while maintaining centralized coordination for key lifecycle management.
Data Source
AI summary
A client system may generate a new key pair for a secrets management process. The client may generate a shared secret using the private key of the new key pair and a public key of a secrets management server. Using the shared secret, the client may derive an encryption key and encrypt a data payload for subsequent decryption by the secrets management server. Upon encryption of the data payload, the client may erase the private key. Subsequently, the client or an associated client may call the secrets management server for decryption of the data payload. The secrets management server may derive the encryption key using the public key associated with the encrypted payload and the private key of the secrets management server and use the encryption key to decrypt the data payload for use by the client or an associated client.