Skip to content

[Gateway] TLS FedRAMP compliance #20927

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Mar 18, 2025
Merged

[Gateway] TLS FedRAMP compliance #20927

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
99d4f2a
Add FedRAMP section
maxvp Mar 18, 2025
097b11f
Add Mermaid chart
maxvp Mar 18, 2025
931b730
Add further explanation
maxvp Mar 18, 2025
dafc5ba
Add call out in top explanation
maxvp Mar 18, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 29 additions & 3 deletions src/content/docs/cloudflare-one/policies/gateway/http-policies/tls-decryption.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Cloudflare Gateway can perform [SSL/TLS decryption](https://www.cloudflare.com/l

When you turn on TLS decryption, Gateway will decrypt all traffic sent over HTTPS, apply your HTTP policies, and then re-encrypt the request with a [user-side certificate](/cloudflare-one/connections/connect-devices/user-side-certificates/).

Cloudflare prevents interference by decrypting, inspecting, and re-encrypting HTTPS requests in its data centers in memory only. Gateway only stores eligible cache content at rest. All cache disks are encrypted at rest. You can configure where TLS decryption takes place with [Regional Services](/data-localization/regional-services/) in the [Cloudflare Data Localization Suite (DLS)](/data-localization/).
Cloudflare prevents traffic interference by decrypting, inspecting, and re-encrypting HTTPS requests in its data centers in memory only. Gateway only stores eligible cache content at rest. All cache disks are encrypted at rest. Traffic on-ramped to Gateway with the WARP client will egress from [FedRAMP compliant data centers](#fedramp-compliance). You can configure where TLS decryption takes place with [Regional Services](/data-localization/regional-services/) in the [Cloudflare Data Localization Suite (DLS)](/data-localization/).

Cloudflare supports connections from users to Gateway over TLS 1.1, 1.2, and 1.3.

Expand Down Expand Up @@ -115,9 +115,35 @@ When FIPS compliance is enabled, Gateway will only choose [FIPS-compliant cipher

FIPS-compliant traffic defaults to [HTTP/3](/cloudflare-one/policies/gateway/http-policies/http3/). To enforce HTTP policies for UDP traffic, you must turn on the [Gateway proxy for UDP](/cloudflare-one/policies/gateway/http-policies/http3/#enable-http3-inspection).

### Cipher suites
## FedRAMP compliance

<GlossaryDefinition term="cipher suite" />
When you use the WARP client to on-ramp TLS traffic to Gateway, traffic will egress from a Cloudflare data center within Cloudflare's FedRAMP boundary. If a user's closest data center is non-FedRAMP compliant, their traffic will still egress from a FedRAMP compliant data center, maintaining FedRAMP compliance for the traffic.

```mermaid
flowchart LR
subgraph s1["Non-FedRAMP data center"]
n2["WARP TLS encryption terminated"]
end
subgraph s2["FedRAMP data center"]
n3["Gateway TLS encryption (FIPS) terminated"]
end
subgraph s3["Private internal network"]
n5["FedRAMP-compliant cloudflared"]
n6(["Private server"])
end
n1(["User near non-FedRAMP compliant data center"]) -- Gateway TLS connection wrapped with WARP TLS --> n2
n2 --> n3
n3 --> n4(["HTTPS server"])
n5 --> n3 & n6

n5@{ shape: rect}
```

To further control what data centers traffic egresses from, you can use [dedicated egress IPs](/cloudflare-one/policies/gateway/egress-policies/dedicated-egress-ips/).

## Cipher suites

<GlossaryDefinition term="cipher suite" prepend="A cipher suite is " />

The following table lists the default cipher suites Gateway uses for TLS decryption.

Expand Down