Titan is Google's hardware security family. The name covers several different products that share the philosophy of dedicated silicon for security-critical operations. Titan M is a custom security chip in Pixel phones that handles secure boot, key storage, and platform integrity. Titan Security Key is a USB and NFC authentication device for personal and enterprise use. Titan chips also live in Google's data centers, anchoring the security of cloud infrastructure.
Google has been one of the most active companies in post-quantum cryptography deployment. Chrome was the first major browser to ship hybrid post-quantum TLS in 2023. Google Cloud Load Balancing offers post-quantum cipher suites. Google's internal infrastructure uses hybrid post-quantum protocols for encryption between data centers. Yet the Titan hardware itself, like other secure enclave technologies, has not yet shipped public post-quantum cryptography.
This article walks through what Google Titan is, what it does today, and where the public information points for post-quantum support. The information is drawn from Google's published documentation at cloud.google.com, security.google.com, and the Pixel security pages.
Titan family overview
The Titan name applies to several distinct products. Titan M is the security chip in Google Pixel phones starting with the Pixel 3. It is a separate microcontroller that handles secure boot verification, lockout enforcement, biometric template protection, and key storage. Titan M2, introduced with the Pixel 6, is a more capable successor.
Titan Security Key is a hardware authentication device that supports the FIDO U2F and FIDO2 protocols. It comes in USB-A, USB-C, and NFC variants. Inside, the Titan Security Key is similar in concept to other FIDO authenticators, but Google has stated that the firmware was developed in-house with attention to supply chain security.
Titan chips in Google's data centers anchor the firmware integrity of servers, network equipment, and other infrastructure. Google does not publish detailed specifications for these data center Titan chips, but the security blog and several published papers describe the architecture at a high level.
OpenTitan, an open-source silicon root of trust project, started from a foundation that included Google contributions. OpenTitan is a separate project from Google's proprietary Titan products, although the philosophical lineage is clear. We cover OpenTitan in OpenTitan: Open-Source Silicon Root of Trust and PQC.
What Titan M does
In a Pixel phone, Titan M is the gatekeeper for secure boot and for key storage. The boot process verifies signatures on the bootloader and on Android system images using keys stored in Titan M. The chip prevents the phone from booting if the signatures do not match Google's published values.
Titan M also enforces the lockout policy for screen unlock attempts. After a configured number of failed attempts, the chip enforces an increasing delay between further attempts. Even if the application processor is compromised, the lockout cannot be bypassed because Titan M counts the attempts independently.
For application keys, Titan M acts as a Keystore backend. Android applications can request hardware-backed keys that are bound to specific authentication factors and to the device. Operations on these keys happen inside Titan M. The application processor never sees the private key material.
Titan M has its own random number generator, its own non-volatile storage, and its own dedicated communication interface to the application processor. The boundary is similar in concept to a TPM but tightly integrated with Android.
What Titan Security Key does
Titan Security Key is a FIDO authenticator. It implements the FIDO U2F protocol for legacy second-factor authentication and the FIDO2 protocol for passwordless authentication. The internal architecture is similar to other FIDO devices, with a secure element handling cryptographic operations.
When a user registers a Titan key with a website or service, the device generates a fresh key pair specific to that relationship. The public key is sent to the service. The private key remains on the Titan key. When the user authenticates, the device produces a signature using the stored private key.
Current Titan keys use elliptic curve cryptography. The signatures are ECDSA over P-256, following the FIDO specification. The keys do not currently support post-quantum signatures, although the FIDO Alliance is working on post-quantum extensions to the protocol.
For the Titan key product specifically, the firmware on the chip determines the algorithms supported. Future hardware revisions could support post-quantum signing. Software-only updates to existing hardware are limited by chip capabilities.
YubiKey integration covers a related FIDO authenticator and how QNSQY uses hardware tokens for credential protection.
Google's data center security
Google publishes a security overview of its data center infrastructure at cloud.google.com/docs/security. The high-level design uses Titan-class chips on every server motherboard for hardware root of trust. The chip verifies the firmware on the server before letting it boot.
For data center operations, Google has implemented hybrid post-quantum cryptography at the network layer. Encryption between data centers uses hybrid protocols that combine classical and post-quantum components. The exact algorithms have evolved as standardization progressed, with current deployments using ML-KEM-based hybrids.
Google's published direction is that post-quantum cryptography is part of the long-term security posture for cloud infrastructure. The roadmap indicates progressive integration through the late 2020s as standards stabilize and as supporting hardware becomes available.
Chrome and post-quantum TLS
While not directly Titan hardware, Chrome's post-quantum TLS deployment is part of Google's broader strategy. Chrome shipped hybrid post-quantum TLS in 2023, using a combination of X25519 and Kyber, the predecessor to ML-KEM. As ML-KEM was finalized, Chrome migrated to use the standardized variant.
The Chrome implementation uses the X25519MLKEM768 hybrid key agreement, which provides both classical and post-quantum security. Servers that support this hybrid see the negotiation in TLS handshakes from Chrome users. Server operators can enable the hybrid on their side to provide post-quantum protection for their users.
This deployment is significant because Chrome's user base is large enough that the hybrid handshake represents a real share of internet traffic. The protocol behavior, including handshake failure modes and middlebox compatibility, has been validated at scale.
Post-quantum direction for Pixel and Titan M
Pixel phones run Android, which is starting to integrate post-quantum cryptography at various layers. Android's keystore APIs are being extended to support post-quantum algorithms. The actual hardware support depends on the underlying chip.
Titan M on existing Pixel phones uses classical cryptography. Future hardware revisions could include post-quantum support, although Google has not publicly committed to a timeline. Software-only post-quantum operations could run in the application processor or in TrustZone, providing a layer of post-quantum protection above what Titan M offers.
For users of Pixel phones today, the practical reality is that Android post-quantum support is expanding through software updates. The Titan M chip continues its existing role for hardware-backed key storage, with the post-quantum migration likely to come in future hardware generations.
Google Cloud confidential computing
Google Cloud offers confidential computing on AMD-based Confidential VMs and Intel TDX-based Confidential VMs. The Titan-rooted server infrastructure underlies both options. Customer workloads in confidential VMs run on hardware whose firmware is verified by Titan chips at boot time.
For post-quantum support in confidential computing, Google Cloud's roadmap aligns with the underlying hardware vendors. As Intel TDX and AMD SEV-SNP gain post-quantum attestation, Google Cloud customers will benefit. The Titan-anchored infrastructure provides the foundation that the post-quantum confidential computing layer builds on.
Intel SGX, Intel TDX, AMD SEV: PQC Status covers the confidential computing landscape in more detail.
OpenTitan and the open-source angle
OpenTitan is a related but separate project from Google's proprietary Titan. OpenTitan is an open-source silicon design for a hardware root of trust, hosted by lowRISC. The design is documented at opentitan.org and the code is available under permissive licenses.
OpenTitan includes cryptographic primitives that are currently classical, with post-quantum extensions on the project roadmap. The open-source nature means that the post-quantum direction is publicly visible through the project's issue tracker and design documents.
For users who want a transparent hardware root of trust with a clear post-quantum path, OpenTitan is a unique option. The project is supported by lowRISC, Google, and several other contributors.
Android Keystore and post-quantum
The Android Keystore is the API that Android applications use to store cryptographic keys. On Pixel phones, Keystore operations can be backed by Titan M for hardware protection. Other Android phones use different secure elements, often integrated into the SoC's TrustZone environment.
For post-quantum support in Android Keystore, several layers need updates. The Keystore API needs to support post-quantum algorithm identifiers. The underlying secure element firmware needs to support the operations. The Android system services need to validate post-quantum keys correctly.
Google has been actively working on this through Android development cycles. Each major Android release brings additional cryptographic support, with hybrid post-quantum likely to appear in upcoming versions. Pixel-specific features tend to ship first, with broader Android support following.
For developers building applications today, the practical guidance is to use the Keystore API rather than implementing cryptography directly. Applications using the API benefit from post-quantum support automatically as the platform layer migrates.
Internet-scale post-quantum deployment
Google's Chrome and Google Cloud TLS deployments collectively cover a significant fraction of internet traffic. The hybrid post-quantum cipher suites have been validated at scale, with millions of connections per day exercising the protocol behavior.
This scale matters because it surfaces issues that smaller deployments would miss. Middlebox compatibility, handshake size limits, retry behavior, and many other operational details have been tested through the volume of Chrome and Google Cloud traffic. The lessons learned inform broader internet adoption of post-quantum protocols.
For organizations migrating their own services to hybrid post-quantum TLS, Google's deployment provides reference data. Server operators can enable the same hybrid cipher suites and expect compatible behavior. Issues that appear in smaller deployments often have known workarounds from Google's at-scale testing.
Practical implications
For Pixel users, the post-quantum security story is primarily software for now. Android updates bring post-quantum cryptography in TLS, in messaging applications that adopt it, and in file-level encryption tools. The hardware Titan M chip continues its existing role.
For Google Cloud users, the post-quantum story spans multiple layers. TLS to Google services is increasingly post-quantum. Internal data center protocols are migrating to post-quantum. Confidential computing is following its own timeline.
For Titan Security Key users, current keys use classical signatures. Future FIDO post-quantum support will require either firmware updates or new hardware. The FIDO Alliance is working on the specifications.
For organizations that need post-quantum protection for files at rest today, software tools like QNSQY provide the most direct path. QNSQY's hybrid post-quantum file format does not depend on Titan or other vendor-specific hardware, making it portable across Google, Apple, Microsoft, and Linux environments.
How QNSQY complements Titan
QNSQY is software, Titan is silicon, but they can work together. A user encrypting files with QNSQY can store the encryption key in Android Keystore on a Pixel phone, with hardware backing through Titan M. The post-quantum protection of the file content is independent of the key storage hardware, but the combination provides defense in depth.
For enterprises, QNSQY can be combined with FIDO authentication using Titan Security Keys. The Titan key authenticates the user. QNSQY encrypts the file. Both layers provide independent security guarantees.
For Google Cloud workloads, QNSQY can run inside virtual machines, including confidential VMs. The post-quantum cryptography protects data at rest. The confidential computing infrastructure protects data during processing. Together they provide post-quantum security across the data lifecycle.
Frequently asked questions
Does Titan M support post-quantum cryptography today? No, not in current production. Titan M uses classical cryptography. Future hardware revisions may add post-quantum support, although Google has not publicly committed to a timeline.
Does Titan Security Key support post-quantum signatures? No, current Titan keys use classical ECDSA. The FIDO Alliance is working on post-quantum extensions, with implementations expected in future hardware revisions.
Is Chrome's post-quantum TLS related to Titan? Indirectly. Chrome's post-quantum TLS is part of Google's broader cryptographic strategy. The same overall direction informs Titan and other Google security products, but Chrome's TLS is a software-only deployment.
What is the difference between Titan and OpenTitan? Titan is Google's proprietary silicon for security. OpenTitan is an open-source silicon design hosted by lowRISC with Google as one of several contributors. OpenTitan has a public post-quantum roadmap.
Can I use Titan with QNSQY? QNSQY runs as software and does not currently integrate directly with Titan. However, encryption keys for QNSQY can be stored in Android Keystore on Pixel phones, gaining hardware backing through Titan M.
Sources
- Google Cloud Security Documentation, https://cloud.google.com/docs/security
- Google Security Blog, https://security.googleblog.com/
- Pixel Security Documentation, https://support.google.com/pixelphone/
- Titan Security Key Information, https://cloud.google.com/titan-security-key
- NIST FIPS 203, Module-Lattice-Based Key-Encapsulation Mechanism Standard, https://csrc.nist.gov/pubs/fips/203/final
- NIST FIPS 204, Module-Lattice-Based Digital Signature Standard, https://csrc.nist.gov/pubs/fips/204/final
- Chrome Post-Quantum TLS Blog Posts, https://blog.chromium.org/
Related Articles
- Secure enclaves and PQC
- OpenTitan: Open-Source Silicon Root of Trust and PQC
- YubiKey integration
- Apple Secure Enclave and PQC
- Microsoft Pluton: PQC Roadmap
Protect Your Data Before Q-Day Arrives
QNSQY's NIST-standardized post-quantum encryption protects files against both current and quantum-era threats.