Hybrid Batch Processing Security via Node Encryption
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current batch processing in cloud environments faces challenges such as security risks due to data exposure and lack of flexibility, particularly in hybrid cloud setups where on-premise servers can become overloaded while cloud resources remain underutilized, and there are no effective techniques for secure batch processing in distributed environments.
Innovation Solution
A method and system for processing batch jobs that involve assigning tasks to different computing nodes with unique public keys, encrypting inputs using these keys, and dispatching encrypted messages, ensuring that sensitive data is only accessible to nodes that need it, thereby enhancing security and flexibility by allowing data processing both on-premise and in the cloud.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If data is distributed across multiple cloud servers and datacenters to improve processing scalability, then batch job processing capacity increases, but security risks increase due to data exposure across multiple locations
Solution Approach 1:
The patent segments batch jobs into multiple tasks that can be independently assigned to different computing nodes. Each task processes a portion of the data, allowing the system to distribute processing across multiple cloud servers while maintaining security through selective data placement and encryption at each node.
Solution Approach 2:
The patent introduces a batch coordinator as an intermediary component that manages task assignment and data distribution. The coordinator orchestrates the interaction between the batch job submission system and distributed computing nodes, controlling data flow and ensuring secure distribution without requiring direct access to all nodes.
2Object-affected harmful factors
If sensitive computations are run only on on-premise servers to improve security, then data confidentiality is maintained, but flexibility and resource utilization decrease when cloud resources are available
Solution Approach 1:
The patent applies local quality by assigning different security levels and access controls to different computing nodes based on their location (on-premise vs. cloud). Sensitive computations are routed to on-premise nodes with higher security protections, while less sensitive tasks can utilize cloud resources, optimizing both security and resource utilization.
Solution Approach 2:
The patent implements dynamic task assignment where the batch coordinator can adjust computing node selection based on real-time conditions including security requirements, resource availability, and task sensitivity. This allows the system to adapt between using only on-premise resources or incorporating cloud resources depending on the batch job's security needs.
3Ease of operation
If distributed computing nodes are placed behind the organization's firewall to improve security management, then administrative control is simplified, but system homogeneity increases and management flexibility decreases
Solution Approach 1:
The patent creates a universal batch processing framework that can operate with computing nodes both inside and outside the organization's firewall. The batch coordinator and task assignment mechanism provide a unified interface for managing heterogeneous environments, allowing the system to incorporate diverse computing resources without requiring uniform administrative control methods.
Data Source
AI summary
An example method for processing a batch job that includes a plurality of sequentially ordered tasks includes obtaining a message that includes inputs of a plurality of tasks included in a batch job. The plurality of tasks includes a first task that is sequentially ordered before a second task. The method also includes assigning tasks of the plurality of tasks to different computing nodes. The first task is assigned to a first computing node associated with a first public key, and the second task is assigned to a second computing node associated with a second public key.


