Symmetric Key Generation via HSM Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional methods for securing customer data in multi-tenant database environments face challenges such as slow asymmetric key cryptography, security risks due to persisted private keys, and vulnerability to quantum computing attacks, particularly when using RSA encryption and hardware security modules (HSMs).
Innovation Solution
The system generates a symmetric key using a key derivation function based on a public key, salt value, and private key, where the private key is stored securely on a security server, and the symmetric key is cached on the application server for encryption and decryption, reducing the need for persistent key storage and enhancing security against quantum computing threats.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If asymmetric key cryptography is used to encrypt customer data, then data security is improved, but encryption speed deteriorates
Solution Approach 1:
The encryption process is divided into two segments: asymmetric key cryptography is used only for encrypting the symmetric key (key wrap), while the actual customer data is encrypted using symmetric key cryptography. This segmentation allows each cryptographic method to be used for its optimal purpose, maintaining security while improving performance.
Solution Approach 2:
A symmetric key acts as an intermediary between the asymmetric key pair and the customer data. The public key encrypts the symmetric key, and the symmetric key then encrypts the data. This intermediary approach resolves the contradiction by using asymmetric cryptography only where needed for key protection, not for bulk data encryption.
2Ease of operation
If private keys are persisted on application servers for key derivation, then key management flexibility is improved, but security against unauthorized access deteriorates
Solution Approach 1:
The private key is extracted from the application server environment and stored exclusively in the hardware security module (HSM). This extraction eliminates the security risk of persisted private keys on application servers while maintaining key management flexibility through the HSM's secure key derivation services.
Solution Approach 2:
The HSM acts as an intermediary that holds the private key securely and performs key derivation operations without exposing the private key to the application server. This mediator approach allows flexible key management through remote key derivation while maintaining high security by keeping the private key isolated in the HSM.
3Reliability
If RSA encryption with HSMs is used, then quantum computing attack resistance is improved, but device complexity and cost deteriorate
Solution Approach 1:
The complexity of quantum-resistant cryptography is extracted and centralized in the HSM, which handles post-quantum cryptographic algorithms. This extraction allows the application server to benefit from quantum attack resistance without directly implementing complex quantum-resistant cryptographic operations, reducing overall system complexity.
Solution Approach 2:
The HSM serves as an intermediary that implements quantum-resistant cryptographic operations on behalf of the application server. By delegating these complex operations to the HSM, the system achieves quantum computing attack resistance while the application server maintains relative simplicity in its cryptographic implementation.
Data Source
AI summary
Methods and systems for securing customer data in a multi-tenant database environment are described. A key identifier received from a security server may be stored by an application server. The key identifier may be associated with a private key that is accessible by the security server and not accessible by the application server. A request to derive a symmetric key may be transmitted from the application server to the security server, the request including a public key generated by the application server, a salt value, and the key identifier. The symmetric key may then be derived based on the transmitted public key and the private key using a key derivation function. The application server may then receive and store the symmetric key in an in-memory cache, and be used to securely encrypt data received by the application server from client devices.