Performance evaluation reveals resource constraints of post-quantum cryptography in satellite systems, highlighting implementation challenges for securing space infrastructure.
Satellite systems rely on a robust yet light weight cryptographic solution for the security of ground systems, communications links, Telemetry, Tracking and Command (TT&C), payloads, onboard systems and associated subsystems. Cryptography ensures data integrity and overall security especially for satellites whose missions and data transmitted are in general and by global practices included in Critical National Infrastructures (CNIs). But emerging cybersecurity threats might render cryptographic solutions such as Rivest-Shamir-Adleman (RSA), Diffie–Hellman (DH) and Elliptic-Curve Cryptography (ECC) ineffective in securing space assets. Quantum cryptography offers a better solution to the emerging threats of relentless and sophisticated systems and adversaries. This paper evaluates the performance of Post-Quantum Cryptography (PQC) when deployed. The research explored the various standards mapped out by the National Institute of Standards and Technology (NIST) for PQC deployment. Current security architecture of satellite systems was compared to what the PQC solution will offer to these highly classified assets. The paper further explored algorithms in place and how effective they could be in the space industry. In the space sector, deploying PQC requires a beta analysis of its performance; which was explored in the third chapter of this work. Challenges and Deployment Considerations and Computational and Resource Constraints of PQC deployment was evaluated in the fifth and sixth sections of this work. The paper concluded by acknowledging the potential complexities in the eventual wholistic adoption and deployment of Quantum Cryptography.
No takes yet. Share an insight, caveat, or question.
Madugu et al. (2026) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: