Homomorphic Encryption for Secure Indirect Fire Data Computation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems for indirect fire protocols face challenges in securely transmitting and computing enemy target locations over unsecure cloud networks, particularly in remote areas where internet connectivity is limited and data transmission requires encryption to prevent unauthorized access.
Innovation Solution
The implementation of a cloud-based system using homomorphic encryption, specifically the Brakerski-Gentry-Vaikuntanathan (BGV) cryptosystem, allows for secure computation and transmission of indirect fire data by encrypting data at the point of generation, enabling secure computation on untrusted cloud infrastructure and protecting against quantum attacks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If data is transmitted over unsecure cloud networks for indirect fire operations, then connectivity and operational capability are improved, but data security and confidentiality deteriorate
Solution Approach 1:
Data is encrypted at the point of generation (Forward Observer) before transmission to the cloud, performing the security action in advance. This preliminary encryption ensures that even if the cloud is compromised, the data remains protected throughout transmission and storage.
Solution Approach 2:
Homomorphic encryption acts as an intermediary mechanism that allows the untrusted cloud to process data without being able to read or understand the actual information. The encryption scheme mediates between the need for cloud processing and the requirement for data security.
2Reliability
If data is encrypted at the point of generation using homomorphic encryption, then data security is improved, but computational complexity and processing time worsen
Solution Approach 1:
The patent replaces traditional encryption-decryption-computation cycles with homomorphic encryption that allows direct computation on encrypted data. This substitution eliminates the need to decrypt data for processing, fundamentally changing the computational approach.
Solution Approach 2:
The system works with encrypted copies of the data throughout the entire processing chain. The cloud processes a copy of the encrypted data without needing the original plaintext, and the results remain encrypted until final decryption at the authorized endpoint.
3Productivity
If cloud-based computation is used for target location calculation, then operational efficiency is improved, but vulnerability to insider threats and quantum attacks worsens
Solution Approach 1:
The system prepares for potential cloud compromise by implementing quantum-resistant homomorphic encryption beforehand. This cryptographic cushioning protects against both current and future quantum computing threats, as well as insider threats, without affecting operational efficiency.
Solution Approach 2:
The patent employs lattice-based homomorphic encryption schemes that are computationally efficient and can be implemented with standard cloud infrastructure. The encryption keys and parameters can be frequently rotated and replaced without significant cost or operational disruption.
Data Source
AI summary
Indirect fire protocol according to several embodiments of the present invention can include the initial step establishing a grid and locating a forward observer (FO) and a firing unit (FU) in the grid. The FO can estimate the bearing and range to a High Value Target (HVT) within the grid, and can homomorphically encrypting said HVT estimated position data. FO can then transmit the encrypted HVT estimated position data over cloud network architecture to a Fire Direction Center (FDC), using the FDC's Keypublic. The FDC can outsource the calculation of an absolute position of said HVT in said grid to non-secure internet cloud architecture, but with encrypted HVT estimation data and the FO position data in the grid (which the FDC knows). Once calculated, the HVT encrypted absolute position data can be decrypted, and then transmitted from FDC to a FU, using the FU's Keypublic.


