Security Boundary Key Management for Computing Device Boot

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Computing devices face challenges in securely communicating data between trusted and untrusted security boundaries, leading to user dissatisfaction due to difficulties in isolating sensitive information during device interactions.

Innovation Solution

The implementation of multiple security boundaries on computing devices, where public/private key pairs are generated and managed during booting, with private keys provided to operating system modules and public keys to a secure cryptoprocessor, enabling secure communication channels and authentication with remote devices while keeping data inaccessible between boundaries.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple security boundaries are implemented to isolate sensitive information, then security and data protection are improved, but device complexity and difficulty of operation worsen

Engineering Contradiction:
ImprovesecurityVSAvoiddevice complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system divides the computing device into multiple security boundaries (first security boundary, second security boundary, third security boundary) with distinct access levels. Each boundary contains specific programs and data with defined accessibility rules, creating a segmented architecture that isolates sensitive information while maintaining controlled communication channels between boundaries.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The operating system module acts as an intermediary between security boundaries, managing key distribution and access control. The boot measurement system serves as another intermediary that verifies the integrity of security boundaries during booting, mediating trust relationships without requiring direct complex interactions between all components.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If multiple security boundaries are implemented to isolate sensitive information, then security and data protection are improved, but ease of operation worsens

Engineering Contradiction:
ImprovesecurityVSAvoidease of operation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system implements automated security boundary verification during booting, where the boot measurement system automatically measures and verifies the integrity of security boundaries without requiring manual user intervention. Key distribution and access control are also automated through the operating system module, reducing operational burden on users.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Security boundaries and their integrity verification are established during the booting process before the system becomes fully operational. This preliminary setup ensures security is in place before any user operations occur, and the boot measurement system pre-verifies the integrity of security boundaries, eliminating the need for users to manually configure security settings.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If public keys are provided to boot measurement system for verification, then authentication reliability is improved, but processing time during booting increases

Engineering Contradiction:
ImproveauthenticationVSAvoidbooting time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Public keys are distributed to the boot measurement system during the booting process in advance of verification operations. The boot measurement system receives and stores public keys from security boundaries early in the boot sequence, allowing subsequent authentication operations to proceed efficiently without repeated key distribution delays.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10229272B2Identifying security boundaries on computing devices
Publication Date: 2019.03.12 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10229272B2 patent drawing
  • US10229272B2 patent drawing
  • US10229272B2 patent drawing

AI summary

During booting of a computing device, multiple security boundaries are generated. A security boundary refers to a manner of operation of a computing device or a portion of the computing device, with a program executing in one security boundary being prohibited from accessing data and programs in another security boundary. As part of booting the computing device measurements of (e.g., hash values or other identifications of) various modules loaded and executed as part of booting the computing device are maintained by a boot measurement system of the computing device. Additionally, as part of booting the computing device, public/private key pairs of one of the security boundaries is generated or otherwise obtained. Private keys of the public/private key pairs are provided to the one security boundary, and the public keys of the public/private key pairs are provided to the boot measurement system.