Enclave Database Logical Logging Under TEE Memory Limits
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional hardware-enabled encrypted database (H-EDB) systems face limitations in achieving fully hardware encrypted (F-HE) architectures due to enclave memory constraints and high input/output costs, leading to suboptimal performance and data security vulnerabilities.
Innovation Solution
Implementing a fully hardware encrypted (F-HE) database system by residing the entire database management system (DBMS) within a trusted execution environment (TEE) memory, using logical log encoding and generation to ensure data privacy and security, and employing Remote Attestation-Transport Layer Security (RA-TLS) for network transmission.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the entire DBMS is moved into the TEE to achieve fully hardware encryption, then data security is improved, but TEE memory limitations prevent complete implementation
Solution Approach 1:
The system segments the database components into two parts: critical components (DBMS engine, data structures, redo logs) are placed inside the TEE enclave for security, while non-critical components remain outside. This segmentation allows the system to achieve security for sensitive operations without requiring the entire system to fit within limited TEE memory.
Solution Approach 2:
The patent introduces an intermediary encoding mechanism for logical logs that operates at the boundary between the TEE enclave and external storage. This intermediary layer encrypts and encodes data before it leaves the secure enclave, allowing external storage to be used without compromising security.
2Reliability
If client-side cryptography is used for privacy protection, then data security is improved, but system complexity and performance overhead increase
Solution Approach 1:
The patent extracts the cryptography functionality from the client side and relocates it entirely within the TEE enclave. By taking out the cryptographic operations from the external environment and confining them to the secure hardware boundary, the system eliminates the need for complex client-side key management and cryptographic protocols while maintaining strong security.
3Ease of operation
If redo logs are processed in the conventional P-HE architecture, then operational functionality is maintained, but data leakage vulnerabilities persist
Solution Approach 1:
The patent applies different quality treatments to different parts of the logging system. Redo logs and critical data structures receive full hardware-based encryption and TEE protection, while other less sensitive operations can use conventional logging mechanisms. This local quality differentiation ensures security for critical operations without unnecessarily complicating the entire system.
Data Source
AI summary
A database management system (DBMS) in an enclave for a data privacy preservation database is provided. The system comprising a DBMS engine configured to parse a database command for execution, set an access control status to a first status for a field of the data privacy preservation database when the parsed database command includes the field corresponding to a record in a system catalog table, and log the database command into a logical log. When the access control status is set to the first status and the database command includes a content of the field, the DBMS engine is further configured to log a predetermined identifier, an identification of the field, and a length of the content immediately before the content in the logical log.