Mutation-less OPE for Secure Database-as-a-Service

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database-as-a-service (DBaaS) systems face challenges in maintaining data security and performance due to the computational expense of Order-Preserving Encryption (OPE) mutations, which lead to increased re-encryption of data, conflicts with concurrent operations, and reduced system throughput and latency.

Innovation Solution

Implementing a mutation-less OPE scheme that generates variable-length cipher texts and dynamically adjusts encryption parameters based on implicit statistics, allowing for efficient range queries and index creation over encrypted data without re-encrypting existing user data, using multiple independent OPE instances and hyperparameter tuning.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If Order-Preserving Encryption (OPE) mutations are performed to maintain security, then security guarantees are improved, but computational expense and system latency increase

Engineering Contradiction:
Improvesecurity guaranteesVSAvoidsystem latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by maintaining encryption state and parameters in memory before mutations are needed. When data is inserted or updated, the system checks whether mutation is actually required by comparing against the maintained state, avoiding unnecessary re-encryption operations and reducing latency while preserving security guarantees.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent extracts the computationally expensive mutation operations from the regular data path by maintaining a separate encryption state in memory. This allows the system to avoid performing full re-encryption for every data modification, instead only updating the extracted state information, thereby reducing computational expense and system latency while maintaining IND-OCPA security.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If OPE mutations are performed frequently to maintain encryption security, then security is improved, but system throughput decreases

Engineering Contradiction:
Improveencryption securityVSAvoidsystem throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary actions by pre-computing and caching encryption parameters and maintaining encryption state in memory. This preliminary preparation allows the system to handle data modifications without triggering expensive mutation operations, thereby maintaining encryption security while preserving system throughput.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The encryption system serves itself by maintaining its own state and parameters in memory, automatically determining when mutations are actually necessary. This self-service mechanism eliminates the need for frequent forced re-encryption operations, maintaining security while avoiding throughput degradation from unnecessary computational overhead.

Inventive Principle:
Principle #25Self-service

3Reliability

If re-encryption of existing user data is performed to update encryption parameters, then security is improved, but computational expense increases

Engineering Contradiction:
ImprovesecurityVSAvoidcomputational expense
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent extracts the essential security-maintaining functionality from full re-encryption by separating encryption parameter updates from data re-encryption. The system maintains encryption state and parameters independently in memory, allowing security to be updated without the computational expense of re-encrypting existing user data, while still providing the necessary security guarantees.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system performs preliminary actions by pre-computing encryption parameters and maintaining them in memory before they are needed for actual encryption operations. This allows the system to update encryption state without re-encrypting user data, reducing computational expense while maintaining security through the pre-prepared encryption parameters.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11860868B2Secure database-as-a-service system
Publication Date: 2024.01.02 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11860868B2 patent drawing
  • US11860868B2 patent drawing
  • US11860868B2 patent drawing

AI summary

Methods, systems, and computer program products for a secure database-as-a-service are provided herein. A computer-implemented method includes obtaining, by a database service, data associated with one or more client devices to be stored in at least one encrypted database; encrypting, without mutation and in accordance with one or more security requirements, at least a portion of the data using an order preserving encryption scheme, wherein the encrypting comprises (i) computing a set of encryption parameters for the portion of the data and (ii) applying a process that converts a fixed-length cipher text corresponding to the portion of the data to a variable-length cipher text; and storing the encrypted data in the at least one encrypted database, wherein the database service enables one or more indexes to be built over the encrypted data to improve performance of query processing.