Aircraft On-Board Equipment Secure Data Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing on-board equipment in vehicles, particularly in the aeronautical field, faces challenges in updating sensitive security data like PKI parameters without requiring a new certification cycle, which is costly and time-consuming due to the integration of these data into the firmware, limiting flexibility and increasing operational risks.
Innovation Solution
A method involving a secure module external to the equipment for storing and authenticating sensitive security data, allowing the firmware to access these data securely without direct integration into the firmware's binary code, enabling updates without hardware modifications and maintaining security through symmetric key authentication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If sensitive security data is integrated into firmware binary code, then security is improved, but adaptability deteriorates
Solution Approach 1:
The system separates sensitive security data from the firmware binary code by storing them in distinct locations. The firmware resides in read-only memory while sensitive data is stored separately in rewritable memory, allowing independent updates of security parameters without modifying the firmware itself.
Solution Approach 2:
Sensitive security data is extracted from the firmware binary code and stored externally in rewritable memory. This extraction allows the firmware to remain unchanged while enabling flexible updates of security parameters through separate data loading operations.
2Reliability
If sensitive security data is integrated into firmware, then security is improved, but ease of manufacture deteriorates
Solution Approach 1:
The system divides the security architecture into firmware (read-only) and security data (rewritable memory). This segmentation simplifies manufacturing by allowing standard firmware production while enabling flexible post-manufacturing updates of security parameters without requiring complex re-certification processes.
3Adaptability or versatility
If sensitive security data is stored in rewritable memory, then adaptability is improved, but reliability deteriorates
Solution Approach 1:
An authentication mechanism acts as an intermediary between the rewritable memory containing sensitive data and the firmware. This intermediary verifies the authenticity and integrity of loaded data through cryptographic validation, ensuring that only authorized and uncorrupted data can be accessed, thus maintaining security while enabling adaptability.
Solution Approach 2:
The system replaces physical security measures (such as hardware security modules or secure enclaves) with a software-based authentication and verification mechanism. This substitution allows flexible data updates while maintaining security through cryptographic protocols rather than physical constraints.
4Adaptability or versatility
If firmware is modified to update security data, then adaptability is improved, but loss of time deteriorates
Solution Approach 1:
Security data is extracted from the firmware and stored separately in rewritable memory. This extraction enables independent updates of security parameters without requiring firmware modification, thereby eliminating time-consuming re-certification cycles and allowing rapid adaptation to new security requirements.
Solution Approach 2:
The system performs preliminary authentication and verification of security data before loading it into rewritable memory. This preliminary action ensures that updates can be applied rapidly without requiring subsequent validation steps, reducing overall update time while maintaining security.
Data Source
Figure 1
Figure 2
Figure 3~7
AI summary
The method involves connecting an external secure module (40) e.g. secure universal serial bus key, comprising a sensitive security data necessary for secure processing, to an on-board equipment (10) of an aircraft. The secure module is authenticated by a micro software (22). A symmetric encryption key is shared for secure module and the on-board equipment item, where the symmetric key is stored in a rewritable memory zone of the on-board equipment of the aircraft. Independent claims are also included for the following: (1) an on-board equipment item provided with a micro software program (2) a system for operating an on-board equipment comprising a secure module.