Skip to content

Commit 5398cfc

Browse files
committed
proxy
1 parent 06ec980 commit 5398cfc

File tree

6 files changed

+8
-8
lines changed

6 files changed

+8
-8
lines changed

src/content/docs/cloudflare-one/insights/logs/gateway-logs/manage-pii.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Cloudflare Gateway can log the following types of PII:
2323

2424
Enabling this setting means Cloudflare Gateway will log activity without storing any employee PII. Changes to this setting will not change PII storage of any previous logs. This means if Exclude PII is enabled and then disabled, there will be no PII data for logs captured while Exclude PII was enabled. The PII data will be unavailable to all roles within your Zero Trust organization, including the Super Admin.
2525

26-
To enable or disable this setting, log in to [Zero Trust](https://one.dash.cloudflare.com/) and go to **Settings** > **Network** > **Exclude PII**.
26+
To enable or disable this setting, log in to [Zero Trust](https://one.dash.cloudflare.com/) and go to **Traffic policies** > **Traffic settings** > **Exclude personally identifiable information (PII) from logs**.
2727

2828
## Redact PII
2929

src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-infrastructure-access.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -129,7 +129,7 @@ To turn off SSH command logging, delete your uploaded public key:
129129
<Tabs>
130130
<TabItem label="Dashboard">
131131

132-
1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **Network** > **SSH encryption public key**.
132+
1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Traffic policies** > **Traffic settings** > **SSH log encryption public key**.
133133

134134
2. Select **Remove**.
135135

src/content/docs/cloudflare-one/traffic-policies/egress-policies/dedicated-egress-ips.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,8 +20,8 @@ An account can have any number of additional dedicated egress IPs. To request ad
2020
To start routing traffic through dedicated egress IPs:
2121

2222
1. Contact your account team to obtain a dedicated egress IP.
23-
2. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **Network**.
24-
3. In **Firewall**, turn on **Proxy**.
23+
2. In [Zero Trust](https://one.dash.cloudflare.com), go to **Traffic policies** > **Traffic settings**.
24+
3. Turn on **Allow Secure Web Gateway to proxy traffic**.
2525
4. Select **TCP**.
2626
5. (Optional) Select **UDP**. This will allow HTTP/3 traffic to egress with your dedicated IPs.
2727

src/content/docs/cloudflare-one/traffic-policies/network-policies/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -318,7 +318,7 @@ The inferred network protocol based on Cloudflare's [protocol detection](/cloudf
318318
<Render file="gateway/selectors/protocol" product="cloudflare-one" />
319319

320320
:::note
321-
To enable Gateway filtering on TCP and UDP, go to **Settings** > **Network** > **Proxy**. Network policies apply to all enabled protocols unless you use the **Protocol** selector within a policy.
321+
To enable Gateway filtering on TCP and UDP, go to **Traffic policies** > **Traffic settings** > **Allow Secure Web Gateway to proxy traffic**. Network policies apply to all enabled protocols unless you use the **Protocol** selector within a policy.
322322
:::
323323

324324
### Proxy Endpoint

src/content/docs/learning-paths/secure-internet-traffic/configure-device-agent/enable-proxy.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,8 +11,8 @@ import { Render } from "~/components";
1111

1212
## Enable the proxy
1313

14-
1. Go to **Settings** > **Network**.
15-
2. Enable **Proxy** for TCP.
14+
1. Go to **Traffic policies** > **Traffic settings**.
15+
2. Enable **Allow Secure Web Gateway to proxy traffic** for TCP.
1616
3. (Recommended) To proxy all port `443` traffic, including internal DNS queries, select **UDP**.
1717
4. (Optional) To scan file uploads and downloads for malware, [enable anti-virus scanning](/cloudflare-one/traffic-policies/http-policies/antivirus-scanning/).
1818

src/content/partials/cloudflare-one/tunnel/troubleshoot-private-networks.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ Determine whether the user is matching any policy, or if they are matching a pol
6464

6565
## 6. Are the correct Gateway proxy settings enabled?
6666

67-
Under **Settings** > **Network**, ensure that **Proxy** is enabled for TCP, UDP, and ICMP traffic. UDP is required for proxying DNS traffic and other UDP packets, while ICMP is required for `ping` and other administrative functions.
67+
Under **Traffic policies** > **Traffic settings**, ensure that **Allow Secure Web Gateway to proxy traffic** is enabled for TCP, UDP, and ICMP traffic. UDP is required for proxying DNS traffic and other UDP packets, while ICMP is required for `ping` and other administrative functions.
6868

6969
## 7. Is the user's traffic reaching the tunnel?
7070

0 commit comments

Comments
 (0)