Homomorphic Encryption Engine for Multi-Cloud Translytical Data Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current enterprise data security measures are inefficient, expensive, and fail to protect against data breaches due to single iteration encryption processes, lack of continuous encryption, and insufficient real-time security measures, making enterprise data vulnerable to attacks.

Innovation Solution

Implementing a self-auto homomorphic encryption engine in a multi-cloud environment using an elastic hybrid memory cube to continuously encrypt enterprise data, apply multiple encryption rules, and use dynamic public and private key pairs to ensure secure, real-time data access control.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If single iteration encryption is used, then processing speed is improved, but security reliability deteriorates

Engineering Contradiction:
Improveprocessing speedVSAvoidsecurity reliability
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent implements continuous multi-iteration encryption where data undergoes multiple encryption cycles with different keys. The encryption process is not a single-pass operation but continues through multiple iterations, ensuring that data remains protected throughout its entire lifecycle in the system, thus resolving the contradiction between processing speed and security reliability.

Inventive Principle:
Principle #20Continuity of useful action

Solution Approach 2:

The encryption process is segmented into multiple discrete iterations, each using a different encryption key. Data is divided into multiple encryption stages rather than being processed in a single pass, allowing each segment to be secured independently while maintaining overall security throughout the data lifecycle.

Inventive Principle:
Principle #1Segmentation

2Device complexity

If single authorization method is used, then system complexity is reduced, but security reliability deteriorates

Engineering Contradiction:
Improvesystem complexityVSAvoidsecurity reliability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The authorization system is segmented into multiple independent authorization levels, each governed by its own policy. Rather than relying on a single authorization method, the system divides authorization into discrete layers that can be independently configured and enforced, reducing the risk that a single point of failure compromises overall security.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a temporal dimension to authorization by implementing time-varying access policies. Authorization decisions are not static but change over time based on predefined policies, creating multiple authorization states across different time dimensions. This multi-dimensional approach enhances security reliability without proportionally increasing system complexity.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Productivity

If data is stored in data pool without immediate processing, then processing efficiency is improved, but security reliability deteriorates

Engineering Contradiction:
Improveprocessing efficiencyVSAvoidsecurity reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary encryption actions on data immediately upon receipt, before data is stored in the data pool. By encrypting data in advance and applying continuous encryption throughout its lifecycle, the system ensures that even when data resides in storage pools for extended periods, it remains protected. This preliminary and continuous security processing prevents security vulnerabilities during storage without compromising processing efficiency.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If continuous multi-key encryption is implemented, then security reliability is improved, but device complexity increases

Engineering Contradiction:
Improvesecurity reliabilityVSAvoiddevice complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements self-service automation in key management and policy enforcement. Automated key rotation, continuous encryption operations, and policy-based access control reduce the need for manual intervention and complex configuration management. The system serves itself by automatically managing the complexity of multi-key encryption without requiring proportionally increased operational complexity from users.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent creates a universal encryption framework that handles multiple encryption keys and authorization policies through a single integrated system. Rather than requiring separate mechanisms for each encryption key or authorization level, the system provides multi-functional capabilities that manage diverse security requirements through unified processes, reducing overall device complexity despite enhanced security requirements.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS12627463B2Using automatic homomorphic encryption in a multi-cloud environment to support translytical data computation using an elastic hybrid memory cube
Publication Date: 2026.05.12 BANK OF AMERICA CORP
  • US12627463B2 patent drawing
  • US12627463B2 patent drawing
  • US12627463B2 patent drawing

AI summary

Aspects of the disclosure relate to using automatic homomorphic encryption in a multi-cloud environment to support translytical data computation using an elastic hybrid memory cube. A computing platform may receive enterprise data from a data collection engine associated with an enterprise organization. The computing platform may inspect the enterprise data and discard enterprise data that fails to satisfy validation criteria. The computing platform may attach encryption rules to the remaining enterprise data. The computing platform may divide the enterprise data into discrete components and may continuously encrypt each component of the enterprise data using public keys. The computing platform may generate private keys that can be used to access the encrypted enterprise data, and may transmit the private keys to the enterprise organization. The computing platform, upon receipt of a private key from the enterprise organization, may determine whether the private key is authorized to access the encrypted enterprise data.