Aircraft File Upload Integrity Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for uploading files onto aircraft are vulnerable to tampering and corruption, as they cannot detect changes to database files that do not alter the original checksum, leaving the onboard system unable to verify the integrity of uploaded data.
Innovation Solution
A system that includes a communication system and a processor onboard the aircraft, which computes and verifies message authentication codes and cyclic redundancy checks for uplinked files, ensuring their integrity by comparing these values with those generated by the ground unit, and rejecting files that fail verification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a database file is uploaded along with its checksum to the aircraft, then the upload process is simple and fast, but the system cannot detect tampering or corruption when an attacker changes the database file in a way that does not alter the original checksum
Solution Approach 1:
The system performs preliminary actions by computing a second checksum independently on the received database file before acceptance. This preliminary verification step ensures that the file integrity is confirmed without delaying the upload process, as the checksum computation is performed in parallel with the file reception.
Solution Approach 2:
The system implements feedback by comparing the first checksum (uploaded with the file) against the second checksum (computed locally). This feedback mechanism provides automatic verification of data integrity, allowing the system to detect tampering and reject corrupted files automatically without manual intervention.
2Reliability
If high assurance software is used to detect malicious data, then data security is improved, but the system becomes costly
Solution Approach 1:
The system uses inexpensive, lightweight checksum algorithms (such as CRC32 or MD5) instead of expensive high-assurance cryptographic software. These disposable-style algorithms provide sufficient security for the application while being computationally efficient and cost-effective to implement on aircraft avionics systems.
Solution Approach 2:
The system changes the security parameter from complex cryptographic verification to simpler checksum-based verification. By adjusting the verification mechanism to use standard checksum algorithms with appropriate key management, the system achieves adequate security without the cost and complexity of high-assurance software.
3Reliability
If the onboard system computes and verifies checksums for uploaded files, then data integrity is improved, but the processing time and computational resources increase
Solution Approach 1:
The system performs the checksum computation as a preliminary action during the file reception process. The second checksum is computed in parallel with the file download, so that by the time the file is fully received, the checksum verification is already complete, minimizing the total time loss.
Solution Approach 2:
The system uses partial verification by computing only the necessary checksum values required for integrity verification, rather than performing exhaustive analysis. This partial action approach provides sufficient security verification without unnecessary computational overhead, balancing reliability with processing time.
Data Source
AI summary
Embodiments described herein provide for a system for verifying integrity of files uplinked to a remote vehicle. The system is configured to receive a first message authentication code (MAC) for the uplinked file, a first acknowledgement MAC for the MAC, and a first cyclic redundancy check (CRC) for the first MAC and the acknowledgement MAC. The system is also configured to compute a second MAC from the uplinked file, a second acknowledgement MAC from the second MAC and a second CRC from the second MAC and second acknowledgement MAC. Integrity of the uplinked file is verified by comparing the first CRC with the second CRC. If integrity of the uplinked file is confirmed, the uplinked file is accepted. If integrity of the uplinked file is not confirmed, the uplinked file is rejected.