Untrusted Boot Image Detection via WORM Memory Indicator

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Computing devices face challenges in determining whether they have booted from an untrusted image, which can alter or damage trusted images and create security vulnerabilities, making it difficult to maintain network security and ensure authorized access to resources.

Innovation Solution

Implementing a computing device with a Write-Once, Read-Many (WORM) memory device or similar tamper-proof indicator to permanently mark if an untrusted image has been booted, allowing applications to restrict access and functionality based on this status.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a computing device allows booting from untrusted images to enable customization and flexibility, then adaptability is improved, but security and system integrity deteriorate

Engineering Contradiction:
Improveboot flexibilityVSAvoidsystem integrity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary verification of the boot image signature before allowing the boot process to proceed. The firmware checks whether the image signature matches an authorized key pair in the authorized list before transferring control to the boot image, preventing untrusted images from executing while still allowing trusted custom images to boot.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary verification layer between the boot image and the system firmware. This intermediary checks the digital signature of the boot image against authorized keys and only permits execution if verification succeeds, thus mediating between the desire for boot flexibility and the need for system integrity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If untrusted images are allowed to boot for customization purposes, then ease of operation is improved, but vulnerability to harmful factors increases

Engineering Contradiction:
Improvecustomization easeVSAvoidsecurity vulnerability
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The system applies preliminary anti-action by preemptively blocking untrusted boot images through signature verification before they can execute harmful code. The firmware actively prevents booting of images with invalid or unauthorized signatures, countering potential security threats before they can manifest.

Inventive Principle:
Principle #9Preliminary anti-action

Solution Approach 2:

An intermediary signature verification mechanism is introduced that stands between the user's boot request and the actual boot execution. This intermediary checks whether the boot image signature is authorized and only permits booting if the verification succeeds, thus protecting against security vulnerabilities while maintaining ease of customization for trusted images.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If the system verifies image signatures before booting, then security is improved, but device complexity increases

Engineering Contradiction:
Improveboot securityVSAvoidverification complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent stores authorized public keys as a list in the firmware, creating a reference copy of trusted identifiers. Instead of implementing complex verification algorithms, the system simply compares the boot image signature against this pre-stored list of authorized keys, significantly simplifying the verification process while maintaining security.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The verification mechanism changes the parameter being checked from complex behavioral analysis to simple signature matching. By verifying digital signatures against a list of authorized keys rather than analyzing system behavior, the patent reduces verification complexity while maintaining high security standards.

Inventive Principle:
Principle #35Parameter changes

4Reliability

If trusted image integrity is maintained through verification, then reliability is improved, but loss of information about custom modifications increases

Engineering Contradiction:
Improveimage integrityVSAvoidcustomization information
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent segments the boot image into distinct components: the signature portion for verification and the payload portion for customization. This segmentation allows the system to verify the signature for integrity while preserving and executing the customized payload, thus maintaining both reliability and customization information.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system copies the authorized public key list into the firmware, creating a reference for verification that doesn't interfere with the custom boot image content. This copying approach allows verification of integrity while preserving the custom modifications in the boot image payload.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9064118B1Indicating whether a system has booted up from an untrusted image
Publication Date: 2015.06.23 GOOGLE LLC
  • US9064118B1 patent drawing
  • US9064118B1 patent drawing
  • US9064118B1 patent drawing

AI summary

Systems, methods, and machine-readable media for indicating that a system has booted an untrusted image are provided. The system may be configured to receive instructions to boot up an image and determine whether the image to be booted up is untrusted. If the image is untrusted, the system may set an indicator to indicate that the system has booted from an untrusted image and booting the image.