Skip to content

Commit e756577

Browse files
committed
Add HTTP partial
1 parent f1eeb6b commit e756577

File tree

3 files changed

+35
-35
lines changed

3 files changed

+35
-35
lines changed

src/content/docs/cloudflare-one/policies/gateway/initial-setup/http.mdx

Lines changed: 2 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -35,22 +35,9 @@ To filter HTTP requests from a device:
3535
params={{ one: "HTTP", two: "requests" }}
3636
/>
3737

38-
## 3. Add recommended policies
38+
## 3. Create your first HTTP policy
3939

40-
To create a new HTTP policy, go to **Gateway** > **Firewall policies** > **HTTP** in Zero Trust.
41-
We recommend adding the following policies:
42-
43-
### Bypass inspection for incompatible applications
44-
45-
Bypass HTTP inspection for applications which use [embedded certificates](/cloudflare-one/policies/gateway/http-policies/tls-decryption/#inspection-limitations). This will help avoid any incompatibilities that may arise from an initial rollout. By the _Do Not Inspect_ app type, Gateway will filter any new applications when they are added to the group.
46-
47-
<Render file="gateway/policies/do-not-inspect-applications" />
48-
49-
### Block all security categories
50-
51-
Block [known threats](/cloudflare-one/policies/gateway/domain-categories/#security-categories) such as Command & Control, Botnet and Malware based on Cloudflare's threat intelligence.
52-
53-
<Render file="gateway/policies/block-security-categories" />
40+
<Render file="gateway/get-started/create-http-policy" />
5441

5542
## 4. Add optional policies
5643

src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/create-policy.mdx

Lines changed: 4 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -13,26 +13,10 @@ Now that you have considered which devices and applications TLS inspection shoul
1313

1414
Use a standard naming convention when building all policies. Policy names should be unique across the Cloudflare account, follow the same structure, and be as descriptive as possible.
1515

16-
To create a new HTTP policy:
17-
18-
1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Gateway** > **Firewall policies**.
19-
20-
2. In the **HTTP** tab, select **Add a policy**.
21-
22-
3. Name the policy.
23-
24-
4. Under **Traffic**, build a logical expression that defines the traffic you want to allow or block.
25-
26-
5. Choose an **Action** to take when traffic matches the logical expression. For example, if you have enabled TLS inspection, some applications that use [embedded certificates](/cloudflare-one/policies/gateway/http-policies/tls-decryption/#inspection-limitations) may not support HTTP inspection, such as some Google products. You can create a policy to bypass inspection for these applications:
27-
28-
<Render
29-
file="gateway/policies/do-not-inspect-applications"
30-
product="cloudflare-one"
31-
/>
32-
33-
6. Select **Create policy**.
34-
35-
For more information, refer to [HTTP policies](/cloudflare-one/policies/gateway/http-policies/).
16+
<Render
17+
file="gateway/get-started/create-http-policy"
18+
product="cloudflare-one"
19+
/>
3620

3721
## Order your policies
3822

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
---
2+
{}
3+
---
4+
5+
import { Render } from "~/components";
6+
7+
To create a new HTTP policy:
8+
9+
1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Gateway** > **Firewall policies**.
10+
2. In the **HTTP** tab, select **Add a policy**.
11+
3. Name the policy.
12+
4. Under **Traffic**, build a logical expression that defines the traffic you want to allow or block.
13+
5. Choose an **Action** to take when traffic matches the logical expression. For example, if you have enabled TLS inspection, some applications that use [embedded certificates](/cloudflare-one/policies/gateway/http-policies/tls-decryption/#inspection-limitations) may not support HTTP inspection, such as some Google products. You can create a policy to bypass inspection for these applications:
14+
15+
<Render
16+
file="gateway/policies/do-not-inspect-applications"
17+
product="cloudflare-one"
18+
/>
19+
20+
Cloudflare also recommends adding a policy to block [known threats](/cloudflare-one/policies/gateway/domain-categories/#security-categories) such as Command & Control, Botnet and Malware based on Cloudflare's threat intelligence:
21+
22+
<Render
23+
file="gateway/policies/block-security-categories"
24+
product="cloudflare-one"
25+
/>
26+
27+
6. Select **Create policy**.
28+
29+
For more information, refer to [HTTP policies](/cloudflare-one/policies/gateway/http-policies/).

0 commit comments

Comments
 (0)