Secure Boot Data Verification via Segmented Key Check

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing security mechanisms for secure boot-up processes in automobile electronics and other software-defined systems are inadequate in reducing attack feasibility, as they often rely on proof-of-work (PoW) methods that can be compromised through manipulation of cryptographic keys during the boot-up process, potentially allowing malware introduction.

Innovation Solution

A method for loading data during the boot-up process that involves a comprehensive check of a character string, which can include a cryptographic key or hash value, to verify data integrity, with optional incorporation of a proof-of-work to enhance scalability and security, using electronic fuses for irreversible modifications to detect manipulations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If proof-of-work (PoW) methods are used for secure boot-up, then computational constraints are applied to prevent denial-of-service attacks, but the security can be compromised through manipulation of cryptographic keys during boot-up

Engineering Contradiction:
ImprovesecurityVSAvoidkey manipulation vulnerability
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The verification process is segmented into multiple independent stages: first verifying the cryptographic key itself, then using that verified key to verify the boot-up data. This segmentation ensures that even if one part is compromised, the overall security is maintained because the key verification is a separate, foundational step that prevents key manipulation attacks.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The cryptographic key is verified before the boot-up data is loaded. This preliminary verification action ensures that the key used for subsequent data verification is trustworthy, preventing attackers from introducing malware by manipulating keys during the boot-up process.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If comprehensive check of entire character string is performed, then attack feasibility is reduced, but processing time and computational resources increase

Engineering Contradiction:
Improvedata integrity verificationVSAvoidboot-up time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The character string is verified in its entirety before the boot-up process proceeds to load data. This preliminary comprehensive verification ensures data integrity is established early, preventing any potential security issues from affecting the boot-up time of subsequent operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Instead of repeatedly verifying the same data during different boot-up stages, the comprehensive character string verification is performed once as a foundation, and the verified results are used throughout the boot-up process, avoiding redundant verification time.

Inventive Principle:
Principle #26Copying

3Reliability

If multiple verification steps are implemented, then security against malware introduction is enhanced, but device complexity increases

Engineering Contradiction:
Improvemalware protectionVSAvoidverification process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The verification process is divided into clear, sequential steps: key verification first, then data verification using the verified key. This segmentation makes the complex security process more manageable and implementable, with each step having a specific, well-defined purpose that reduces overall complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The cryptographic key acts as an intermediary element that connects the verification of boot-up data to the loading process. By using the verified key as a mediator, the system achieves enhanced malware protection without requiring direct complex verification of all data, simplifying the overall verification architecture.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20240155336A1Vehicle, device, computer program and method for loading data
Publication Date: 2024.05.09 INFINEON TECHNOLOGIES AG
  • US20240155336A1 patent drawing
  • US20240155336A1 patent drawing
  • US20240155336A1 patent drawing

AI summary

The present disclosure relates to a vehicle, a device, a computer program and a method for loading data, e.g., during a boot-up process. The method includes a reception of at least one character string for the verification of data. The method further includes a verification of data, wherein the verification of data includes a comprehensive check of the entire character string. The method further provides for a loading of data based on the check of the character string.