User-Controlled Firmware Locking for Trusted Virtual Machines

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users are concerned about the confidentiality and trustworthiness of virtual machines hosted in environments where they cannot verify the firmware, leading to potential vulnerabilities and data security risks.

Innovation Solution

A hosting environment allows users to select and control their own firmware, which is locked against changes without user permission, and includes a virtual trusted platform module for encryption, enabling user-controlled firmware deployment and management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the hosting environment uses default firmware with trusted platform modules for encryption, then data confidentiality is improved, but user trust is worsened because users cannot verify the firmware or control changes

Engineering Contradiction:
Improvedata confidentialityVSAvoiduser control over firmware
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The firmware control is segmented into user-controlled portions and hosting environment-controlled portions. Users can select and control specific firmware components (like trusted platform modules) while the hosting environment retains control over other aspects, allowing both confidentiality and user trust to be satisfied simultaneously

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The firmware control model transitions from static (either fully hosting-controlled or fully user-controlled) to dynamic, where users can selectively control specific firmware components based on their trust requirements. The system adapts to user preferences while maintaining hosting environment functionality

Inventive Principle:
Principle #15Dynamics

2Reliability

If the hosting environment allows user-selected firmware, then user trust and confidentiality are improved, but device complexity is worsened due to multiple firmware management requirements

Engineering Contradiction:
Improvefirmware trustworthinessVSAvoidfirmware management system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The firmware management system is designed to handle multiple firmware types and control modes through a unified interface. The same hosting environment infrastructure supports both default firmware and user-selected firmware, reducing the need for separate management systems and minimizing added complexity

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

3Reliability

If the hosting environment locks firmware against changes without user permission, then firmware integrity is improved, but ease of operation is worsened due to additional permission management steps

Engineering Contradiction:
Improvefirmware integrityVSAvoidfirmware update process
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

Users are empowered to self-manage their firmware selections and permission settings. The system provides clear interfaces for users to specify which firmware components should be locked and which can be updated, allowing users to configure the level of protection according to their needs without requiring constant hosting environment intervention

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12430160B2User-controlled firmware for hosted virtual machines
Publication Date: 2025.09.30 MICROSOFT TECHNOLOGY LICENSING LLC
  • US12430160B2 patent drawing
  • US12430160B2 patent drawing
  • US12430160B2 patent drawing

AI summary

A computer implemented method includes receiving first firmware information at a hosting environment identifying that a user has selected user-controlled firmware for user virtual machines to be hosted on the hosting environment. A copy of the user-controlled firmware is obtained and a user virtual machine is deployed that includes the user-controlled firmware. The user-controlled firmware is locked against changes by the hosting environment absent receiving permission from the user.