Vehicle Component Software Authorization Using Signed Component Keys
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing development and testing process for vehicle components is cumbersome due to the need for vehicle manufacturers to sign and test software from suppliers and third-party developers, overloading their cryptographic infrastructure and causing delays.
Innovation Solution
Introduce an additional authentication key linked to identification information specific to each vehicle component, allowing developers to cryptographically sign and test software independently without compromising series component security, using a method that includes storing identification information and the authentication key during production, and authenticating the cryptographic signature based on this information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the vehicle manufacturer signs and tests all software from suppliers and third-party developers, then the security and integrity of vehicle software is ensured, but the cryptographic infrastructure becomes overloaded and the development process is delayed
Solution Approach 1:
The authentication authority is segmented between the vehicle manufacturer (who signs the authentication key) and component developers (who sign software). This segmentation allows developers to independently authenticate software without overloading the manufacturer's cryptographic infrastructure, while maintaining security through the manufacturer's ultimate authorization.
Solution Approach 2:
An authentication key acts as an intermediary between the vehicle manufacturer and component developers. The manufacturer signs the authentication key, which then enables developers to cryptographically sign and test software independently. This intermediary mechanism resolves the contradiction by delegating authentication capability while maintaining security oversight.
2Ease of operation
If additional authentication keys are introduced for development purposes, then independent software testing by developers is enabled, but the cryptographic security system becomes more complex
Solution Approach 1:
The authentication key is preliminarily prepared and signed by the vehicle manufacturer before development activities begin. This preliminary action establishes a trusted foundation that enables subsequent independent software testing without requiring complex real-time authentication mechanisms, thereby reducing overall system complexity.
Solution Approach 2:
The authentication key serves multiple functions: it authenticates the developer's identity, enables cryptographic signing of software, and allows independent testing on series components. This multi-functionality reduces the need for separate complex systems for each function, simplifying the overall cryptographic architecture.
3Reliability
If software is signed by the vehicle manufacturer for testing, then cryptographic protection against gray market trading is maintained, but the effort and requirements for the manufacturer's security system increase
Solution Approach 1:
The signing function is extracted from the vehicle manufacturer and delegated to component developers through the authentication key mechanism. The manufacturer extracts only the essential function of authorizing developers via signature, while developers handle the actual software signing. This extraction reduces the manufacturer's security system requirements while maintaining cryptographic protection.
Data Source
AI summary
A method grants authorization to run a computer program using a vehicle component of a vehicle. The method includes storing identification information on the vehicle component as part of a production process, said identification information being specific to the vehicle component. An additional authentication key is stored in the vehicle component during a development process. The additional authentication key is linked to the identification information by means of a cryptographic signature. The method also includes obtaining the computer program for the vehicle component, wherein said computer program is cryptographically signed. The method further includes running the computer program if the cryptographic signature of the computer program is valid according to an authentication process using the additional authentication key and if the cryptographic signature is based on the identification information.