Log Record Deletion via Key Table Encryption
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The increasing complexity of preserving user anonymity in logged data due to expanding data corpora and the need for timely deletion of user-requested information poses challenges in deletion processes, especially with policies requiring retention and analysis intervals.
Innovation Solution
A method and system that identify log records, determine delete requests, generate and store encrypted values using a key table and user activity table, ensuring deletion within specified time frames while maintaining user privacy by minimizing access to keys and user data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If log records are retained for extended periods to maintain data availability, then data accessibility is improved, but user privacy and security are compromised
Solution Approach 1:
The system performs preliminary encryption of log records at the time of ingestion, storing them in encrypted form from the outset. This allows the data to be retained for long periods while maintaining security, as the encryption is already in place before any potential access occurs.
Solution Approach 2:
The patent introduces an intermediary key management system that controls access to encrypted log records. Keys are stored separately and only provided to authorized components when needed, acting as a mediator between data accessibility requirements and privacy protection needs.
2Object-affected harmful factors
If deletion requests are processed immediately upon receipt, then user privacy is protected, but data integrity and policy compliance are compromised
Solution Approach 1:
The system performs preliminary validation and marking of log records for deletion when requests are received, but actual deletion is deferred until analysis intervals complete. This preliminary action ensures privacy protection intent is captured while allowing necessary analysis to proceed.
Solution Approach 2:
The deletion process is made dynamic by adjusting the timing based on policy requirements and analysis intervals. The system flexibly determines when deletion occurs, balancing immediate privacy protection with the need to maintain data integrity for required periods.
3Ease of operation
If encryption keys are stored with encrypted data for easy decryption, then data accessibility is improved, but security is worsened
Solution Approach 1:
The system segments the encryption key management by storing keys separately from encrypted data. Keys are maintained in a distinct key management system rather than being co-located with the data they protect, reducing security vulnerabilities while maintaining accessibility through controlled key provision.
Solution Approach 2:
An intermediary key management system acts as a mediator between encrypted data and decryption operations. This intermediary controls and audits key access, providing secure decryption capability without direct exposure of keys to data storage systems.
4Reliability
If all log records are retained for analysis intervals before deletion, then data integrity is maintained, but storage resources are consumed
Solution Approach 1:
The system performs preliminary identification and marking of log records that are scheduled for deletion based on retention policies. These marked records can be efficiently managed and removed once their retention period expires, optimizing storage usage while maintaining integrity for required periods.
Solution Approach 2:
The system efficiently discards log records that have completed their required retention and analysis periods. By systematically identifying and removing expired records, the system recovers storage resources while maintaining data integrity during the required retention window.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method of deleting log records may include identifying a plurality of log records generated during a time period, for each identified log record, determining whether a delete request associated with the log record has been made, and, in response to determining that a delete request has not been received, identifying a unique identifier associated with the log record, searching a user activity table for an entry having a key table index associated with the unique identifier, where the entry is associated with a timestamp, using the key table index and the timestamp to identify a key associated with the unique identifier and the timestamp from a key table, encrypting at least a portion of the log record with the identified key to generate an encrypted value, and storing the encrypted value as an entry in the log record database that is associated with the identified log record.