Container Hopping Mechanism for Resilient Cloud Process Security
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing container security mechanisms in virtualized environments are inadequate in preventing unauthorized access and maintaining security in cloud-based systems, particularly as technology moves towards increased reliance on containerized systems.
Innovation Solution
A container hopping mechanism is employed, where a virtual container is replicated into a plurality of synchronized replicas, and the software process is moved across these replicas in a pseudo-random sequence defined by a hopping set, incorporating time and port settings, known only to authorized users, to enhance security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a single virtual container is used to run software processes, then the system is simpler to manage and operate, but the security against unauthorized access is insufficient
Solution Approach 1:
The system segments the software process execution across multiple virtual container replicas instead of using a single container. Each replica is an isolated instance that can independently run the software process, creating segmented execution environments that enhance security through distribution.
Solution Approach 2:
The system creates multiple copies (replicas) of the virtual container, each capable of independently running the software process. These replicas serve as interchangeable instances that can be activated or deactivated dynamically, providing redundancy and security against unauthorized access.
2Reliability
If the software process remains stationary in one container, then the operation is simpler, but unauthorized access can be maintained longer by attackers
Solution Approach 1:
The system implements dynamic process migration capability, allowing the software process to move between different virtual container replicas during execution. This dynamic behavior enables the process to relocate from potentially compromised containers to secure ones, maintaining operational continuity while enhancing security.
Solution Approach 2:
The system employs periodic hopping between container replicas according to a predetermined sequence. This periodic relocation prevents attackers from maintaining continuous unauthorized access, as the process systematically moves between containers rather than remaining stationary.
3Reliability
If multiple replicated containers are used with hopping mechanism, then unauthorized access is limited, but the system complexity increases
Solution Approach 1:
The system implements self-service mechanisms where the virtualization layer automatically manages the creation, replication, and coordination of container instances. The hopping sequence and container lifecycle are managed autonomously by the system infrastructure, reducing the operational burden on users despite the increased complexity.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The present disclosure is directed to systems and methods for container security using a hopping mechanism. Methods include the steps of selecting a first virtual container associated with one or more software processes; replicating the first virtual container to create a plurality of replicated virtual containers, each of the plurality of replicated virtual containers a duplicate of the first virtual container, and the plurality of replicated virtual containers configured to run synchronously; generating a randomized hopping set that defines a set of replicated virtual containers from the plurality of replicated virtual containers, the randomized hopping set establishing a sequence of the set of replicated virtual containers in which to run the one or more software processes; and running the one or more software processes across the set of replicated virtual containers based on the sequence of the randomized hopping set.