Boot Sequence Validation via Program Execution Graph
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Vehicle computing systems face vulnerabilities during boot sequences due to limited computational resources and inefficiencies in securing programs, making them susceptible to malicious attacks that can alter vehicle operations or steal sensitive information.
Innovation Solution
A program execution graph (PEG) is pre-generated to track and validate the boot sequence by monitoring characteristics of executing programs, comparing them against the PEG, and generating responses to thwart unauthorized execution, such as halting the boot sequence or reporting malicious activity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If cryptographic hash validation is used to secure programs, then program integrity is improved, but computational load increases and load times extend
Solution Approach 1:
The validation approach is segmented into two distinct phases: (1) pre-computation of cryptographic hashes and creation of the Program Execution Graph (PEG) during program development, and (2) lightweight verification during boot by comparing actual execution sequence against the pre-generated PEG. This segmentation moves the computationally intensive work to the development phase, allowing fast boot validation.
Solution Approach 2:
The PEG is generated in advance during program development, storing the expected execution sequence and cryptographic hashes. During boot, the system only needs to perform lightweight comparison against this pre-computed reference, rather than performing full cryptographic validation of all programs during startup.
2Reliability
If traditional security measures are implemented, then program protection is improved, but system complexity increases
Solution Approach 1:
The system implements feedback by monitoring the actual program execution sequence during boot and comparing it against the expected sequence stored in the PEG. If deviations are detected (indicating potential tampering), the system can trigger security responses. This feedback mechanism provides protection without requiring complex real-time analysis.
Solution Approach 2:
The PEG serves as an intermediary structure that mediates between the programs and the validation process. Instead of directly validating each program's cryptographic integrity, the system uses the PEG as an intermediate reference to verify the execution sequence, simplifying the validation logic.
3Reliability
If comprehensive program validation is performed, then security against malicious attacks is improved, but computational resources are consumed
Solution Approach 1:
The solution extracts the computationally intensive cryptographic validation operations from the boot process and relocates them to the program development phase. During boot, only lightweight sequence verification is performed by comparing the actual execution order against the pre-stored PEG, dramatically reducing computational resource consumption while maintaining security.
Data Source
AI summary
Systems, methods, and other embodiments described herein relate to validating programs of a computing system in a vehicle by tracking a boot sequence. In one embodiment, a method includes, responsive to detecting initiation of a boot sequence in a computing system, tracking characteristics of programs executing as part of the boot sequence. The method includes determining whether the programs correspond with a program execution graph (PEG) by comparing the characteristics of the programs as the programs boot with the PEG. The method includes providing a response to thwart a malicious program when the boot sequence does not match the PEG.