Hypervisor Firewall for Agentless VM Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional systems in virtualized datacenters face challenges in scaling network security due to the resource-intensive nature of personal firewall agents, which can lead to reduced processing capacity and network efficiency, as each virtual machine requires its own instance, and these agents may not effectively prevent lateral spread of compromised workloads within the datacenter.

Innovation Solution

An agentless personal network firewall system that utilizes a hypervisor to monitor and manage communication requests across multiple virtual machines without installing agents within each VM, using a hypervisor firewall application to build virtual machine memory maps and inspect endpoint message criteria to determine access permissions and route or block communications accordingly.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If personal firewall agents are installed on each virtual machine, then network security is improved, but processing capacity and memory resource capacity are reduced

Engineering Contradiction:
Improvenetwork securityVSAvoidprocessing capacity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The firewall functionality is extracted from individual virtual machines and consolidated into the hypervisor layer. The hypervisor now performs centralized firewall operations for all VMs, eliminating the need for separate firewall agents on each VM while maintaining security functionality. This extraction resolves the contradiction by removing the resource overhead from individual VMs while preserving network security at the virtualization layer.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Multiple individual firewall agents across different virtual machines are merged into a single centralized firewall implementation within the hypervisor. This consolidation combines the security functions of numerous distributed agents into one unified system, reducing total resource consumption while maintaining comprehensive network security coverage for all VMs.

Inventive Principle:
Principle #5Merging (Combining)

2Reliability

If personal firewall agents are installed on each virtual machine, then network security is improved, but network efficiency is slowed

Engineering Contradiction:
Improvenetwork securityVSAvoidnetwork efficiency
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

Firewall processing is extracted from the virtual machine network stack and moved to the hypervisor network layer. This allows firewall operations to occur at the virtualization layer without adding processing overhead to individual VM network operations, thereby maintaining network efficiency while preserving security functionality.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The hypervisor firewall provides universal security services to all virtual machines through a single implementation. This multi-functional approach allows the same firewall code to protect multiple VMs simultaneously, eliminating the need for repeated security processing in each VM and improving overall network efficiency.

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

3Reliability

If personal firewall agents are installed on each virtual machine, then network security is improved, but device complexity is increased

Engineering Contradiction:
Improvenetwork securityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The complexity of managing multiple distributed firewall agents is extracted and consolidated into the hypervisor. This centralization simplifies the overall system architecture by replacing numerous independent firewall components with a single managed firewall service, reducing deployment and maintenance complexity while maintaining security.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Multiple separate firewall agent instances are merged into a single hypervisor-based firewall service. This consolidation reduces the number of components that need to be installed, configured, and maintained across the virtualized environment, thereby reducing device complexity while preserving comprehensive security coverage.

Inventive Principle:
Principle #5Merging (Combining)

4Reliability

If personal firewall agents are installed on each virtual machine, then network security is improved, but resource usage is increased

Engineering Contradiction:
Improvenetwork securityVSAvoidmemory resource capacity
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

Firewall functionality is extracted from individual VM memory spaces and implemented in the hypervisor memory. This allows the firewall code to be loaded once in the hypervisor rather than being duplicated in each VM's memory, significantly reducing total memory resource capacity requirements while maintaining security functionality for all VMs.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The memory resources required for firewall operations across multiple VMs are merged into a single allocated memory space in the hypervisor. This consolidation eliminates redundant memory allocations that would occur with distributed agents, reducing overall memory consumption while preserving security capabilities.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS11526373B2Agentless personal network firewall in virtualized datacenters
Publication Date: 2022.12.13 INTERWISE CO LTD
  • US11526373B2 patent drawing
  • US11526373B2 patent drawing
  • US11526373B2 patent drawing

AI summary

Concepts and technologies directed to agentless personal firewall security in virtualized datacenters are disclosed herein. Embodiments can include a computer system that can host a hypervisor via a memory and a processor. Upon execution, the processor can cause the computer system to perform operations. The operations can include receiving an inbound communication request to a virtual machine associated with the hypervisor. The operations also can include identifying a virtual port associated with the virtual machine based on the inbound communication request. The operations can include determining that the inbound communication request lacks an identity of a virtual application process that executes on the virtual machine. The operation also can include building a virtual machine memory map. The operation also can include forcing exposure of the virtual application process based on the virtual machine memory map.