Data Tokenization With External Key Separation for Breach Resistance
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data encryption methods are insufficient in preventing access to encrypted data once a breach occurs, as decryption keys are often stored within the organization, making it vulnerable to unauthorized access.
Innovation Solution
A system that generates a token or replacement data field for sensitive information, encrypts the original data, and stores it with a hash of the token, ensuring that neither the token nor the unencrypted data is stored within the encryption server or database, thereby requiring both to be compromised to access the data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional encryption methods are used with decryption keys stored within the organization, then data can be accessed and used by authorized personnel, but the system becomes vulnerable to breaches as hackers can access both encrypted data and decryption keys
Solution Approach 1:
The system segments the encryption process into two independent parts: encrypted data stored in the organization's database and decryption keys stored externally in a secure key management service. This segmentation ensures that even if the database is breached, the decryption keys remain inaccessible to attackers, thereby resolving the vulnerability while maintaining data accessibility for authorized users.
Solution Approach 2:
The decryption keys are extracted from the organization's internal systems and stored externally in a separate secure key management service. This extraction removes the critical security component (decryption keys) from the potentially vulnerable internal environment, allowing the organization to maintain data accessibility while eliminating the risk of key compromise during a breach.
2Object-affected harmful factors
If decryption keys are stored externally to enhance security, then breach vulnerability is reduced, but system complexity increases due to the need for key management infrastructure
Solution Approach 1:
The system introduces an intermediary key management service that acts as a mediator between the encrypted data in the organization's database and the decryption keys. This intermediary handles all key-related operations securely, providing a standardized interface for key access while managing the complexity of key storage, rotation, and access control externally, thus reducing the burden on the organization's internal systems.
3Reliability
If encryption is implemented to protect data, then data security is improved, but data accessibility and usability may be reduced due to the need for decryption processes
Solution Approach 1:
The system performs preliminary encryption of data before storage, so that data is already protected when stored in the database. Decryption keys are pre-stored in the external key management service with appropriate access controls configured in advance. This preliminary preparation ensures that when authorized users need to access data, the decryption process can proceed smoothly without compromising security, thus maintaining ease of operation for legitimate users.
Data Source
AI summary
A system configured to: accept a data field from a calling service, application, or user; and generate a token or replacement data field for use by the caller instead of the actual data field.