Hybrid Cloud Orchestration With Three-Layer Secure Data Gateway

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing hybrid cloud systems face security risks and data loss issues during data movement between private and public clouds, primarily due to conventional wireless network technologies used for data transfer.

Innovation Solution

Implementing an intelligent hybrid-cloud orchestration engine with a three-layered secure data gateway, utilizing cognitive bulk data analysis, user and entity behavior analytics, advanced encryption, convolution neural networks, and distributed hash tables to optimize data transfer based on sensitivity and eliminate threats without decryption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional wireless network technology is used for data transfer between private and public clouds, then data movement is enabled, but security risks and data loss issues occur

Engineering Contradiction:

Improvedata securityVSAvoidsecurity risks and data loss

Core Design Contradiction:

ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The security gateway is divided into three distinct layers: first security layer for data retrieval and initial analysis, second security layer for encrypted data processing and threat detection, and third security layer for hashing and storage. Each layer performs specific security functions, collectively addressing the security risks of conventional wireless transfer through segmented security controls.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

A security gateway is introduced as an intermediary component between the private cloud and public cloud. This gateway performs multiple security functions including data analysis, encryption, threat detection, and hashing before data transfer occurs, thereby eliminating security risks associated with direct conventional wireless transfer.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If data is encrypted using strong encryption algorithms like AES, then data security is improved, but transfer speed and resource requirements are reduced

Engineering Contradiction:

Improvedata securityVSAvoiddata transfer speed

Core Design Contradiction:

ReliabilityVSSpeed

Solution Approach 1:

Different encryption algorithms are applied to different data based on their sensitivity classification. High-sensitivity data uses AES encryption for maximum security, while less sensitive data uses RSA encryption for faster processing. This localized quality approach optimizes the balance between security and performance for each data type.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The system changes the encryption parameter (algorithm type) based on data sensitivity analysis. By selecting appropriate encryption algorithms (AES or RSA) according to the risk level and sensitivity of each data element, the system optimizes both security strength and transfer performance dynamically.

Inventive Principle:

Principle #35Parameter changes

3Reliability

If comprehensive security analysis and encryption are performed on all data, then data security is improved, but processing time and system complexity increase

Engineering Contradiction:

Improvedata securityVSAvoidprocessing time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

Instead of applying comprehensive security analysis to all data uniformly, the system performs selective security actions based on data sensitivity classification. The security gateway analyzes data elements and applies appropriate security measures (encryption, threat detection, hashing) only where necessary, reducing processing time while maintaining adequate security.

Inventive Principle:

Principle #16Partial or excessive action

Solution Approach 2:

The system performs preliminary data analysis and sensitivity classification before applying security measures. By pre-analyzing data elements to determine their risk levels and sensitivity, the system can apply security processing in an optimized sequence, reducing overall processing time while maintaining security effectiveness.

Inventive Principle:

Principle #10Preliminary action

4Reliability

If threat detection is performed on encrypted data without decryption, then data security is maintained, but detection accuracy may be reduced

Engineering Contradiction:

Improvedata securityVSAvoidthreat detection accuracy

Core Design Contradiction:

ReliabilityVSMeasurement precision

Solution Approach 1:

The system replaces traditional decryption-based threat detection with encrypted data analysis using CNN-LSTM algorithms. Instead of decrypting data to detect threats (mechanical approach), the system analyzes encrypted data patterns directly using neural networks, maintaining security while achieving effective threat detection through substituted detection methodology.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS12457230B2Intelligent hybrid cloud orchestration engine leveraging 3 layered secured data gateway

Publication Date: 2025.10.28 BANK OF AMERICA CORP

AI summary

A hybrid cloud orchestration process to move data from a private to a public cloud is disclosed. Requested data in a private cloud is analyzed to determine risk levels and whether it is fit for transfer based on an initial threat analysis. Data is encrypted by AES or RSA depending on data sensitivity. Redundant data and embedded threats are removed from the encrypted data without decryption. Encrypted data is hashed. Hash keys and hashed data are stored in a DHT distributed across nodes. Data requests from applications in the public cloud are validated by matching the request key with the unique hash key in the individual node containing the corresponding hash data. Data is returned to the application in the public cloud through an encrypted tunnel.