You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/ssl/post-quantum-cryptography/pqc-and-zero-trust.mdx
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,10 @@ Refer to the sections below to learn about the use cases supported by the Zero T
14
14
15
15
[Clientless](/cloudflare-one/connections/connect-devices/agentless/)[Access](/cloudflare-one/applications/configure-apps/self-hosted-public-app/) protects an organization's Internet traffic to internal web applications against quantum threats, even if the applications themselves have not yet migrated to post-quantum (PQ) cryptography.
16
16
17
+
.
18
+
19
+
Here is how it works today:
20
+
17
21
**1. PQ connection via browser**
18
22
19
23
As long as the end-user uses a modern web browser that supports post-quantum key agreement (for example, Chrome, Edge, or Firefox), the connection from the device to Cloudflare's network is secured via TLS 1.3 with post-quantum key agreement.
@@ -34,6 +38,8 @@ A [secure web gateway (SWG)](/learning/access-management/what-is-a-secure-web-ga
34
38
35
39
[Cloudflare Gateway](/cloudflare-one/policies/gateway/http-policies/) is now a quantum-safe SWG for HTTPS traffic. As long as the third-party website that is being inspected supports post-quantum key agreement, then Cloudflare's SWG also supports post-quantum key agreement. This is true regardless of the on-ramp that you use to get to Cloudflare's network, and only requires the use of a browser that supports post-quantum key agreement.
36
40
41
+
.
42
+
37
43
Cloudflare Gateway's HTTPS SWG feature involves two post-quantum TLS connections, as follows:
38
44
39
45
**1. PQ connection via browsers**
@@ -44,5 +50,5 @@ A TLS connection is initiated from the user's browser to a data center in Cloudf
44
50
45
51
A TLS connection is initiated from a data center in Cloudflare's network to the origin server, which is typically controlled by a third party. The connection from Cloudflare's SWG currently supports post-quantum key agreement, as long as the third-party's origin server also already supports post-quantum key agreement. You can test this out by using https://pq.cloudflareresearch.com/ as your third-party origin server.
46
52
47
-
Put together, Cloudflare's SWG is quantum-ready to support secure access to any third-party website that is quantum ready today or in the future.
53
+
Putting it together, Cloudflare's SWG is quantum-ready to support secure access to any third-party website that is quantum ready today or in the future.
0 commit comments