Hypervisor Integrity via On-Chip Authentication and Write Blocking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Hypervisor systems are vulnerable to compromise, allowing unauthorized access to critical resources when multiple operating systems coexist on a computing device, due to potential corruption, memory table manipulation, or improper input/output handling.

Innovation Solution

A secure hypervisor system is implemented using hardware and software strategies, including on-chip and off-chip components, a security processor for authentication and encryption, an instruction checker to verify memory access, and a write blocker to prevent unauthorized modifications to hypervisor page tables, ensuring the hypervisor's integrity and proper resource allocation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a hypervisor system is implemented to manage multiple operating systems, then resource distribution capability is improved, but system security and integrity are worsened due to vulnerability to compromise

Engineering Contradiction:
Improveresource distribution capabilityVSAvoidsystem security and integrity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The hypervisor system is divided into separate functional modules including a security module, authentication module, and resource management module. This segmentation allows the security functions to be isolated and protected independently, preventing compromise of the entire system if one module is vulnerable.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

An authentication module serves as an intermediary between operating systems and critical resources. This intermediary verifies the identity and authorization of operating systems before granting access to resources, preventing unauthorized access while maintaining proper resource distribution.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If memory tables are made accessible to the hypervisor for resource management, then resource allocation flexibility is improved, but system integrity is worsened due to potential memory table corruption

Engineering Contradiction:
Improveresource allocation flexibilityVSAvoidsystem integrity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary authentication and verification of memory tables before the hypervisor accesses them. This preliminary action ensures that only trusted and uncorrupted memory tables are used for resource allocation, preventing integrity issues while maintaining allocation flexibility.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements continuous monitoring and verification feedback mechanisms that detect memory table corruption or unauthorized modifications. When corruption is detected, the system can switch to alternative memory tables or trigger security protocols, maintaining reliable operation while preserving resource allocation flexibility.

Inventive Principle:
Principle #23Feedback

3Object-generated harmful factors

If the hypervisor configures sandbox environments for operating systems, then resource isolation is improved, but security protection is worsened when the hypervisor is compromised or improperly configured

Engineering Contradiction:
Improveresource isolationVSAvoidsecurity protection
Core Design Contradiction:
Object-generated harmful factorsVSObject-affected harmful factors

Solution Approach 1:

The system implements beforehand cushioning by pre-configuring security protocols, authentication mechanisms, and monitoring systems before the hypervisor operates. This ensures that even if the hypervisor is compromised, the pre-established security layers continue to protect critical resources and maintain isolation integrity.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Solution Approach 2:

The security system uses composite materials in the sense of combining multiple security mechanisms (authentication modules, encryption layers, monitoring systems, and isolation protocols) into a unified hypervisor architecture. This composite approach ensures that compromise of one mechanism does not compromise overall security protection.

Inventive Principle:
Principle #40Composite materials

4Ease of operation

If the hypervisor handles input/output operations, then system functionality is improved, but security is worsened due to potential improper input/output handling allowing malicious access

Engineering Contradiction:
Improvesystem functionalityVSAvoidsecurity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

An authentication module serves as an intermediary for all input/output operations between operating systems and critical resources. This intermediary verifies the legitimacy of each I/O operation and blocks malicious access attempts, maintaining proper system functionality while preventing security breaches.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback mechanisms that monitor and verify input/output operations in real-time. This feedback allows the system to detect and respond to improper or malicious I/O handling, maintaining security while preserving necessary system functionality.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10318765B2Protecting critical data structures in an embedded hypervisor system
Publication Date: 2019.06.11 AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE LTD
  • US10318765B2 patent drawing
  • US10318765B2 patent drawing
  • US10318765B2 patent drawing

AI summary

A system and method for securing a hypervisor and operating systems that execute on a computing device. An encrypted hypervisor is uploaded to a hardware chip. Prior to being executed, the hypervisor is decrypted using a secure security processor and stored in an on-chip memory. When a processor on the hardware chip executes the hypervisor, at least one on-chip component continuously authenticates the hypervisor during execution. A hypervisor configures a processor with access rights associated with an operating system, where the access rights determine access of the operating system to an at least one resource. A transaction filter then uses the access rights associated with the operating system to monitor the access of the operating system to the at least one resource in real-time as the operating system executes on a processor.