Cloudflare's announcement about post-quantum TLS certificates this week caused a burst of coverage about just what exactly post-quantum SSL connections are, the coming ability of quantum computing to crack today's encryption ("harvest now / crack later"), and what it looks like to enable PQC SSL for a website. One of the primary reasons we rearchitected our web-facing systems to sit behind GCP's Global External Load Balancer was not for load balancing, but for the GELB's ability to provide SSL termination and insulate us from any common security risks. In fact, Google's managed SSL certificates and GELB actually offer built-in post-quantum support. As each of our websites and APIs moves behind the load balancer (such as this blog), you'll notice that if your browser supports these new standards, it will seamlessly connect to our sites and endpoints using it. Google's load balancer infrastructure handles all of the actual work behind the scenes, meaning we don't have to worry about any of it. Importantly, as these and other web standards continue to evolve, all of our websites and API endpoints will automatically and seamlessly support them – a huge benefit of using the Global External Load Balancer.
Post Quantum TLS With The GCP Global External Load Balancer
