Hypervisor-Based Secure VM Switching for Malware Isolation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing electronic communication systems are vulnerable to malware attacks, which can intercept sensitive information during online transactions, compromising data security and privacy, especially when using hardware virtualization platforms.

Innovation Solution

A host system with a hypervisor that alternates between a client virtual machine and a secure virtual machine, where the client VM performs a wake-to-sleep transition in response to security risks, allowing the secure VM to take over, loaded from a pre-determined core VM snapshot, ensuring exclusive use of peripheral devices for secure data exchange.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a client virtual machine executes on a hardware virtualization platform, then users can access protected resources and exchange data with remote systems, but the system becomes vulnerable to malware attacks that can intercept sensitive information

Engineering Contradiction:
Improveaccess to protected resourcesVSAvoidmalware interception risk
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The system segments the virtual machine environment into two distinct modes: a client VM mode for general operations and a secure VM mode for protected transactions. The hypervisor enforces strict isolation between these modes, ensuring that malware in the client VM cannot intercept data during secure operations. This spatial and functional segmentation resolves the contradiction by providing both accessibility and security.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The hypervisor acts as an intermediary layer between the client VM and the secure VM, controlling all transitions and resource access. It monitors for trigger events indicating security risks and orchestrates the mode switching. This intermediary mechanism enables the system to maintain ease of operation while blocking malware interception attempts through controlled access mediation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If the system switches between client VM and secure VM to enhance security, then data security is improved, but system complexity increases due to hypervisor management and mode switching

Engineering Contradiction:
Improvedata securityVSAvoidhypervisor and mode switching complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system dynamically switches between client VM and secure VM modes based on real-time security conditions detected by trigger events. Rather than maintaining static security configurations, the hypervisor adapts the operational mode according to the security context, enabling high reliability without requiring permanently complex security infrastructure for all operations.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The secure VM is instantiated as a snapshot copy of the client VM configuration, preserving the same hardware interface and operational characteristics while running in an isolated security context. This copying approach allows the system to achieve high security reliability without designing entirely separate complex security systems, as the secure VM replicates the client VM structure with enhanced protection.

Inventive Principle:
Principle #26Copying

3Reliability

If peripheral devices are hidden from the secure VM during initialization, then security is enhanced by preventing malware access, but device availability is reduced when switching modes

Engineering Contradiction:
Improvesecurity isolationVSAvoiddevice availability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

Peripheral devices are hidden from the secure VM during the initialization phase before any security-sensitive operations begin. This preliminary action ensures that malware cannot establish connections to peripheral devices before the secure environment is established. The devices are then revealed when the secure VM becomes active, providing both security isolation and device availability at appropriate times.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The visibility of peripheral devices to the secure VM follows a periodic pattern: hidden during initialization and client VM operation, revealed during secure VM execution. This periodic control of device access ensures that peripherals are only available when the system is in the secure mode, simultaneously achieving security isolation and adaptability based on operational phase.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS9563457B2Enabling a secure environment through operating system switching
Publication Date: 2017.02.07 BITDEFENDER IPR MANAGEMENT
  • US9563457B2 patent drawing
  • US9563457B2 patent drawing
  • US9563457B2 patent drawing

AI summary

Described systems and methods allow a host system, such as a computer or a smartphone, to enable a secure environment, which can be used to carry out secure communications with a remote service provider, for applications such as online banking, e-commerce, private messaging, and online gaming, among others. A hypervisor oversees a switch between an insecure environment and the secure environment, in response to a user input, or in response to an event such as receiving a telephone call. Switching from the insecure to the secure environment comprises transitioning the insecure environment to a sleeping state and loading the secure environment from a memory image (snapshot) saved to disk, after checking the integrity of the snapshot. Switching from the secure to the insecure environment comprises transitioning the secure environment into a sleeping state and waking up the insecure environment.