Skip to content

Commit 9bdeb58

Browse files
committed
Add policy partial
1 parent 03a299b commit 9bdeb58

File tree

4 files changed

+17
-25
lines changed

4 files changed

+17
-25
lines changed

src/content/docs/cloudflare-one/policies/gateway/network-policies/common-policies.mdx

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -6,10 +6,9 @@ sidebar:
66
head:
77
- tag: title
88
content: Common network policies
9-
109
---
1110

12-
import { Render } from "~/components"
11+
import { Render } from "~/components";
1312

1413
The following policies are commonly used to secure network traffic.
1514

@@ -23,12 +22,7 @@ Refer to the [network policies page](/cloudflare-one/policies/gateway/network-po
2322

2423
Require devices to have certain software installed or other configuration attributes. For instructions on enabling a device posture check, refer to the [device posture section](/cloudflare-one/identity/devices/).
2524

26-
In the following example, users can only access an application if they connect from a company device.
27-
28-
| Selector | Operator | Value | Logic | Action |
29-
| ---------------------------- | -------- | ----------------------- | ----- | ------ |
30-
| Passed Device Posture Checks | not in | `Device serial numbers` | And | Block |
31-
| SNI Domain | is | `internalapp.com` | | |
25+
<Render file="gateway/policies/enforce-device-posture" />
3226

3327
## Enforce session duration
3428

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

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -9,25 +9,19 @@ import { Render } from "~/components";
99

1010
DNS policies determine how Gateway should handle a DNS request. When a user sends a DNS request, Gateway matches the request against your filters and either allows the query to resolve, blocks the query, or responds to the query with a different IP.
1111

12-
You can filter DNS traffic based on query or response parameters (such as domain, source IP, or geolocation). You can also filter by user identity if you connect your devices to Gateway with the [WARP client or Cloudflare One Agent](/learning-paths/secure-internet-traffic/connect-devices/install-agent/). To learn more, refer to [DNS policies](/cloudflare-one/policies/gateway/dns-policies/).
12+
You can filter DNS traffic based on query or response parameters (such as domain, source IP, or geolocation). You can also filter by user identity if you connect your devices to Gateway with the [WARP client or Cloudflare One Agent](/learning-paths/secure-internet-traffic/connect-devices/install-agent/).
1313

1414
To create a new DNS policy:
1515

1616
1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Gateway** > **Firewall policies**.
17-
1817
2. In the **DNS** tab, select **Add a policy**.
19-
2018
3. Name the policy.
21-
2219
4. Under **Traffic**, build a logical expression that defines the traffic you want to allow or block.
23-
2420
5. Choose an **Action** to take when traffic matches the logical expression. For example, we recommend adding a policy to block all [security categories](/cloudflare-one/policies/gateway/domain-categories/#security-categories):
25-
2621
<Render
2722
file="gateway/policies/block-security-categories"
2823
product="cloudflare-one"
2924
/>
30-
3125
6. Select **Create policy**.
3226

3327
For more information, refer to [DNS policies](/cloudflare-one/policies/gateway/dns-policies/).
Lines changed: 4 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Create your first DNS policy
2+
title: Create your first network policy
33
pcx_content_type: learning-unit
44
sidebar:
55
order: 1
@@ -14,20 +14,14 @@ You can filter DNS traffic based on query or response parameters (such as domain
1414
To create a new network policy:
1515

1616
1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Gateway** > **Firewall policies**.
17-
1817
2. In the **Network** tab, select **Add a policy**.
19-
2018
3. Name the policy.
21-
2219
4. Under **Traffic**, build a logical expression that defines the traffic you want to allow or block.
23-
24-
5. Choose an **Action** to take when traffic matches the logical expression. For example, we recommend adding a policy to block all [security categories](/cloudflare-one/policies/gateway/domain-categories/#security-categories):
25-
20+
5. Choose an **Action** to take when traffic matches the logical expression.
2621
<Render
27-
file="gateway/policies/block-security-categories"
22+
file="gateway/policies/enforce-device-posture"
2823
product="cloudflare-one"
2924
/>
30-
3125
6. Select **Create policy**.
3226

33-
For more information, refer to [DNS policies](/cloudflare-one/policies/gateway/dns-policies/).
27+
For more information, refer to [network policies](/cloudflare-one/policies/gateway/network-policies/).
Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
{}
3+
---
4+
5+
In the following example, users can only access an application if they connect from a company device:
6+
7+
| Selector | Operator | Value | Logic | Action |
8+
| ---------------------------- | -------- | ----------------------- | ----- | ------ |
9+
| Passed Device Posture Checks | not in | _Device serial numbers_ | And | Block |
10+
| SNI Domain | is | `internalapp.com` | | |

0 commit comments

Comments
 (0)