Challenges for the Post-Quantum Transition of Mobile Ecosystems
summary
Mobile implementations test SPHINCS on a common Snapdragon running Android 11 (Cortex A77/A55) and achieve a 3× speedup by parallelizing Merkle-tree work across cores, using existing DSP/vector units for further gains. No dedicated PQC co-processor or side‑channel protections exist yet, so designs require a secure, high‑performance CPU or new co‑processor, bigger key/storage budgets, and tradeoffs in area, power, and certification for any hybrid interim solution.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:23Mobile hardware PQ challenges
- 3:49Quantum urgency and transition
- 5:36SoC security architecture
- 9:30PQC standards landscape
- 12:17Hardware agility for PQC
- 15:06Side channel risks in PQC
- 16:55Using CPU for PQC
- 21:07High-performance PQC needs
- 22:53PQC hardware trade-offs
- 23:38Qualcomm’s PQC signatures
- 24:19Compliance and testing
- 25:02Hardware changes vs reuse
- 26:26Offloading Keccak for PQC
- 27:08Apple’s PQC strategy
- 27:49Hybrid PQC hardware
- 29:12Closing remarks
related talks
58mPQC Integration in HSMs: From Standards to Strategy
24mOvercoming Challenges in Post-Quantum Cryptography Adoption
30mPQC in Mobile Networks: Insights from the GSMA Task Force
20mASEAN’s Post-Quantum Future: Securing Communications in an Era of Disruptive Change
39mPQC in Action: From Global Standards to Secure Deployments
53mPanel: Migrating to Post-Quantum Schemes
23mReal-World Post-Quantum Migrations: Lessons Learned and Performance Results
15mImplementing Hybrid TLS with ML-KEM-768 for Post-Quantum Security in Mobile IIoT Deployments