Android 17 will incorporate post-quantum cryptography, from initialization to application signatures

Google is integrating post-quantum cryptography into Android 17’s entire trust chain, from the operating system’s boot initialization to the digital signatures of applications distributed via Google Play. This transition, initiated by Google in 2016 and now entering operational deployment, anticipates a future threat that could have retroactive effects: encrypted communications intercepted and stored today might be decrypted tomorrow.

<p>The public-key cryptography that underpins much of our current digital security — from banking transactions to industrial secrets — relies on mathematical problems that classical computers struggle to solve in a reasonable timeframe. This computational resistance forms the foundation of protocols like RSA and elliptic curve algorithms. However, quantum computers harness properties of quantum mechanics — such as superposition and entanglement — enabling them to process multiple states simultaneously, making it feasible to solve these problems at scales unattainable by traditional architectures. The U.S. National Institute of Standards and Technology (NIST) finalized its first post-quantum cryptography standards in 2024; Android 17 marks the first large-scale implementation of these standards within a mainstream mobile operating system.</p>

<p>This issue extends beyond just mobile devices. With billions of active Android units worldwide, a substantial portion is deployed in professional and institutional contexts. Securing their trust chain directly impacts the robustness of business applications, VPN access, strong authentication mechanisms, and the sensitive data flows that traverse these devices daily.</p>

<h4><strong>Securing System Integrity Pre-Application Launch</strong></h4>

<p>The first architectural modification is to Android Verified Boot (AVB), the mechanism that ensures the integrity of the operating system during bootup. Android 17 incorporates the ML-DSA (Module-Lattice-Based Digital Signature Algorithm), one of the algorithms selected by NIST in its finalized post-quantum standards. ML-DSA relies on mathematical problems related to Euclidean lattices, which are known to be resilient against quantum attacks, enabling the generation and verification of digital signatures within a security framework that current elliptic curve algorithms cannot withstand against quantum-equipped adversaries.</p>

<p>The second enhancement pertains to Remote Attestation, a mechanism through which a device cryptographically proves its state to a server or third-party service. Android 17 initiates the migration of KeyMint — the component responsible for certificate chains — to a fully post-quantum-compliant architecture, allowing each device to continue to prove its integrity reliably in an environment where traditional signatures may no longer suffice.</p>

<h4><strong>Developers Generate Post-Quantum Keys from Secure Hardware</strong></h4>

<p>Implementing lattice-based cryptography within a Trusted Execution Environment (TEE) poses significant engineering challenges: the key sizes and memory footprints associated with ML-DSA are considerably larger than those for elliptic curve algorithms, especially in a context where TEE resources are severely constrained. Android 17 offers two security profiles — ML-DSA-65 and ML-DSA-87 — accessible via the standard KeyPairGenerator API, allowing developers to avoid implementing proprietary cryptographic primitives themselves.</p>

<p>This integration at the level of secure hardware is crucial: keys never leave the hardware enclave, minimizing the attack surface to only vectors targeting the TEE itself. For development teams managing strong authentication applications, electronic signatures, or access to sensitive resources, the native availability of ML-DSA within the Android Keystore eliminates the barrier of custom cryptographic implementation and the associated risks.</p>

<h4><strong>A Hybrid Transition for Billions of Active Installations</strong></h4>

<p>The migration of application signing spreads the transition risk across the ecosystem. Google Play automatically generates hybrid signature blocks that combine existing classical keys with the new ML-DSA keys, enabling Android 17 to validate post-quantum signatures on APK files without breaking compatibility for earlier system versions. Developers utilizing Play App Signing benefit from this upgrade automatically for existing applications; those managing their own signing keys will have the option to delegate their ML-DSA keys to Google Play in a later phase of the rollout.</p>

<p>Furthermore, Google Play encourages developers to renew their signing keys at least every two years — a cryptographic hygiene practice that takes on added significance in a post-quantum transition context, where the lifespan of cryptographic materials in circulation directly influences exposure to retroactive risk. The management of signing keys relies on Google Cloud KMS, raising concerns for organizations subject to digital sovereignty requirements regarding dependency on third-party U.S. infrastructure — a point European Chief Information Security Officers will need to factor into their risk assessments.</p>

<h4><strong>Roadmap Extends from Signing to Secure Data Exchange</strong></h4>

<p>Android 17 represents the first phase of a multi-year migration. The roadmap published by Google plans to extend post-quantum cryptography to key encapsulation in KeyMint, as well as key attestation and remote provisioning mechanisms. This evolution will gradually encompass the entire lifecycle of digital identity on the platform, from DICE hardware measures to remote attestation servers.</p>

<p>For security teams managing Android fleets in business, the immediate challenge is to map applications and data flows reliant on signing or attestation mechanisms — to identify those that will automatically benefit from the migration via Play App Signing and those requiring explicit updates. The availability of initial beta versions of Android 17 provides a testing window that should not be overlooked, especially for environments where continuous authentication and signature traceability hold regulatory significance.</p>
Scroll to Top