Cloudflare on Tuesday began allowing customers to secure connections from its global network to their origin servers with post-quantum digital signatures. The move marks the first concrete step in the company’s accelerated push toward full post-quantum security by 2029. It arrives as governments and enterprises scramble to address a shrinking window before quantum computers can undermine today’s public-key infrastructure.
But here’s the catch. This new capability doesn’t activate automatically. Customers must generate fresh certificates using algorithms like ML-DSA-44. They upload them through the dashboard or API. And they reconfigure their origins to enforce strict verification. Nothing flips on its own. The change forces action on systems that many operators had left untouched for years.
The announcement landed in a detailed blog post from the company. It explains the engineering behind supporting Module-Lattice-Based Digital Signature Algorithm signatures in two specific products: Authenticated Origin Pulls and the Custom Origin Trust Store. Cloudflare Blog laid out the configuration steps. It included sample OpenSSL commands that require version 3.5.0 or newer. And it confessed to a production incident on June 10, 2026. That outage stemmed from stricter KeyUsage enforcement in BoringSSL during internal testing.
Why focus here first? The connection between Cloudflare’s edge and a customer’s backend differs sharply from browser-to-edge traffic. Cloudflare acts as the TLS client. It maintains long-lived connection pools. Those pools spread the cost of larger post-quantum signatures across thousands of requests. Performance penalties shrink. Meanwhile the pre-existing business relationship between Cloudflare and its customers sidesteps the rigid timelines of the public WebPKI. No need yet for Merkle Tree Certificates or other innovations still under discussion at the IETF.
Encryption came earlier. Cloudflare turned on hybrid post-quantum key agreement for visitor connections in 2022. It extended similar protection to origins the following year. Over two-thirds of browser traffic now benefits from that defense against harvest-now-decrypt-later attacks. Authentication lagged. Recent advances in quantum hardware and cryptanalysis changed the math. They pulled forward estimates of when a cryptographically relevant quantum computer might appear. Suddenly signatures mattered as much as key exchange.
The National Institute of Standards and Technology released its first three finalized post-quantum standards in August 2024. Those cover ML-KEM for key encapsulation, ML-DSA for signatures, and SLH-DSA as a backup. NIST selected HQC as a fifth algorithm in March 2025. The agency has urged administrators to begin transitioning systems immediately. NIST Post-Quantum Cryptography page carries the message plainly. Organizations cannot afford to wait.
President Trump signed Executive Order 14412 on June 22, 2026. The directive requires federal agencies to complete post-quantum key establishment on high-value assets by the end of 2030. Post-quantum authentication follows one year later. Federal contractors face the same 2030 deadline for compliance with NIST standards. Cloudflare welcomed the order in its own analysis published the next day. Yet the company set a more ambitious internal target. Full post-quantum readiness across all products, including authentication, by 2029.
“We’ve been doing the work the EO is asking federal agencies to do since 2019,” the Cloudflare post stated. It highlighted how the order splits the migration into encryption first, then signatures. Authentication proves harder. Signature sizes balloon. Certificate chains grow. Every relying party, browser, log aggregator and CA must update. Downgrade attacks remain a real risk until classical mechanisms are fully retired.
Cloudflare’s latest release directly tackles that downgrade problem for origin connections. When customers upload only ML-DSA certificate authorities to the Custom Origin Trust Store, the system stops trusting classical roots. The same applies to client certificates presented during mutual TLS. ML-DSA-44 serves as the default recommendation. It delivers NIST security category 2 at lower computational cost than the 65 or 87 variants. For most workloads the performance difference justifies the choice.
Implementation requires care. The private keys must be generated in FIPS 204 seed-only format. Cloudflare accepts nothing else for upload. Origins running NGINX or similar must reference the new certificates and enforce TLS 1.3 only. Verification involves checking server logs for the expected signature algorithm or using packet captures. Direct openssl s_client tests against the origin IP can confirm the handshake details when the server remains reachable.
One production hiccup already revealed the sharp edges. During Cloudflare’s own rollout, a change in how BoringSSL validated KeyUsage extensions in ML-DSA certificates caused brief breakage. The company fixed it quickly. Still the episode underscored a broader truth. Certificate plumbing demands staging environments and thorough testing. Teams cannot treat this as a simple configuration toggle activated on a Friday afternoon.
Industry reaction appeared swiftly on X. Several posts highlighted the July 29 timing and the requirement for customers to manage their own certificate infrastructure. One detailed thread noted that this represents the first piece of Cloudflare’s post-quantum program that actually requires changes on customer-run machines. Previous encryption upgrades had arrived more transparently.
Broader momentum builds. Google has protected internal communications with post-quantum cryptography since 2022 and enabled ML-KEM by default in Chrome for desktop in May 2024. Palo Alto Networks published guidance in January 2026 urging C-suite executives to begin post-quantum planning immediately because migration timelines stretch years. The Cybersecurity and Infrastructure Security Agency released lists of product categories supporting the new standards in response to a 2025 executive order. Governments from Canada to the European Union published national roadmaps targeting completion by 2035.
Yet gaps persist. Many enterprises still run legacy systems that cannot easily accommodate larger signatures or new algorithms. Cloudflare Tunnel offers one workaround. It forwards traffic through a post-quantum-secured path without forcing upgrades on the origin itself. Authentication support for tunnels remains in development. The company also plans to add Merkle Tree Certificate support for origin connections later. That will help customers who prefer to stay within the public WebPKI.
The distinction between encryption and authentication matters. Encryption protects data recorded today from decryption tomorrow. Authentication prevents an adversary with a future quantum computer from forging credentials, impersonating servers or signing malicious code. Both threats matter. But the second arrives later. And it carries different operational weight. Cloudflare now gives customers the tools to address the origin leg of that second problem.
So what comes next? The company continues work on visitor-to-edge post-quantum authentication. Internal systems need upgrades. Additional products will follow. Full coverage by 2029 looks aggressive. It also looks necessary given the revised threat assessments that prompted the accelerated roadmap in April 2026.
Operators who delay risk finding themselves years behind when deadlines tighten further. Those who start now gain breathing room. They learn the operational realities of larger keys and hybrid deployments. They identify dependencies that classical cryptography still hides. And they position their organizations to meet both customer expectations and regulatory requirements that grow stricter each year.
Cloudflare’s rollout won’t solve every problem. It does demonstrate that practical post-quantum authentication can ship today for a well-scoped use case. The rest of the industry will watch closely. Many will follow the configuration patterns published this week. The quantum clock keeps ticking. And the window for orderly transition narrows with each new research paper.
Cloudflare Deploys ML-DSA Signatures for Origin Server Authentication as Quantum Threats Accelerate first appeared on Web and IT News.
