Skip to content

Commit a9525a3

Browse files
committed
Update reference
1 parent 6956d14 commit a9525a3

File tree

2 files changed

+49
-10
lines changed

2 files changed

+49
-10
lines changed

src/content/docs/page-shield/reference/page-shield-api.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ sidebar:
77

88
import { GlossaryTooltip, APIRequest } from "~/components";
99

10-
You can enable and disable Page Shield, configure its settings, and fetch information about detected scripts and connections using the [Page Shield API](/api/resources/page_shield/methods/get/).
10+
You can enable and disable Page Shield's client-side resource monitoring, configure settings, and fetch information about detected scripts and connections using the [Page Shield API](/api/resources/page_shield/methods/get/).
1111

1212
To authenticate API requests you need an [API token](/fundamentals/api/get-started/create-token/). For more information on the required API token permissions, refer to [Roles and permissions](/page-shield/reference/roles-and-permissions/).
1313

@@ -464,7 +464,7 @@ This `GET` request obtains the details of a cookie detected by Page Shield with
464464

465465
### Create a policy
466466

467-
This `POST` request creates a Page Shield policy with _Log_ action, defining the following scripts as allowed based on where they are hosted:
467+
This `POST` request creates a Page Shield policy (or content security rule) with _Log_ action, defining the following scripts as allowed based on where they are hosted:
468468

469469
- Scripts hosted in `myapp.example.com` (which does not include scripts in `example.com`).
470470
- Scripts hosted in `cdnjs.cloudflare.com`.
@@ -476,7 +476,7 @@ All other scripts would trigger a policy violation, but those scripts would not
476476
For more information on <GlossaryTooltip term="content security policy (CSP)">Content Security Policy (CSP)</GlossaryTooltip> directives and values, refer to the [MDN documentation](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy).
477477

478478
:::note
479-
For a list of CSP directives and keywords supported by Page Shield policies, refer to [CSP directives supported by policies](/page-shield/policies/csp-directives/).
479+
For a list of CSP directives and keywords supported by policies, refer to [CSP directives supported by policies](/page-shield/policies/csp-directives/).
480480
:::
481481

482482
<APIRequest

src/content/docs/page-shield/reference/settings.mdx

Lines changed: 46 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,11 @@ sidebar:
55
order: 1
66
---
77

8-
import { GlossaryTooltip } from "~/components";
8+
import { GlossaryTooltip, Tabs, TabItem } from "~/components";
99

1010
## Reporting endpoint
1111

12-
When enabled, Page Shield uses a <GlossaryTooltip term="content security policy (CSP)">Content Security Policy (CSP)</GlossaryTooltip> [report-only HTTP header](/page-shield/reference/csp-header/) to gather information about all the scripts running on your application.
12+
When enabled, Page Shield's client-side resource monitoring uses a <GlossaryTooltip term="content security policy (CSP)">Content Security Policy (CSP)</GlossaryTooltip> [report-only HTTP header](/page-shield/reference/csp-header/) to gather information about all the scripts running on your application.
1313

1414
By default, reports are sent to a Cloudflare-owned endpoint:
1515

@@ -28,17 +28,29 @@ Enterprise customers with a paid add-on can change the reporting endpoint so tha
2828
Using the same hostname for CSP reporting may interfere with other Cloudflare products. Before selecting this option, ensure that your Cloudflare configuration complies with the following:
2929

3030
- No rate limiting rules match the `cdn-cgi/*` URL path
31-
- No WAF custom rules match the `cdn-cgi/*` URL path
31+
- No custom rules match the `cdn-cgi/*` URL path
3232

3333
### Configure the reporting endpoint
3434

3535
To configure the CSP reporting endpoint:
3636

37+
<Tabs syncKey="dashNewNav"> <TabItem label="Old dashboard">
38+
3739
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
3840
2. Go to **Security** > **Page Shield** > **Settings**.
3941
3. Under **Reporting endpoint**, select **Cloudflare-owned endpoint** or **Same hostname**.
4042
4. Select **Apply settings**.
4143

44+
</TabItem> <TabItem label="New dashboard" icon="rocket">
45+
46+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
47+
2. Go to **Security** > **Settings** > **Client-side abuse** tab.
48+
3. Under **Continuous script monitoring** > **Configurations**, select the edit icon next to **Reporting endpoint**.
49+
4. Select **Cloudflare-owned endpoint** or **Same hostname**.
50+
5. Save your changes.
51+
52+
</TabItem> </Tabs>
53+
4254
## Connection target details
4355

4456
When connection targets are reported to Cloudflare, their URIs can sometimes include sensitive data such as session ID.
@@ -47,21 +59,48 @@ By default, Page Shield will only check the domain against malicious threat inte
4759

4860
### Configure the connection target details to use
4961

62+
<Tabs syncKey="dashNewNav"> <TabItem label="Old dashboard">
63+
5064
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
5165
2. Go to **Security** > **Page Shield** > **Settings**.
5266
3. Under **Connection target details**, select **Log host only** to analyze only the hostname or **Log full URI** to use the full URI in Page Shield.
5367
4. Select **Apply settings**.
5468

55-
## Turn off Page Shield
69+
</TabItem> <TabItem label="New dashboard" icon="rocket">
70+
71+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
72+
2. Go to **Security** > **Settings** > **Client-side abuse** tab.
73+
3. Under **Continuous script monitoring** > **Configurations**, select the edit icon next to **Data processing**.
74+
4. Select **Log host only** to analyze only the hostname or **Log full URI** to use the full URI.
75+
5. Save your changes.
76+
77+
</TabItem> </Tabs>
5678

57-
When you turn off Page Shield, you lose visibility on the scripts running on your zone, the outbound connections made from pages in your domain, and cookies detected in HTTP traffic.
79+
## Turn off client-side resource monitoring
5880

59-
To turn off Page Shield:
81+
When you turn off Page Shield's client-side resource monitoring, you lose visibility on the scripts running on your zone, the outbound connections made from pages in your domain, and cookies detected in HTTP traffic.
82+
83+
To turn off client-side resource monitoring:
84+
85+
<Tabs syncKey="dashNewNav"> <TabItem label="Old dashboard">
6086

6187
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
6288
2. Go to **Security** > **Page Shield** > **Settings**.
6389
3. In **Disable Page Shield**, select **Disable**.
6490

91+
</TabItem> <TabItem label="New dashboard" icon="rocket">
92+
93+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
94+
2. Go to **Security** > **Settings** > > **Client-side abuse** tab.
95+
3. Next to **Continuous script monitoring**, select the toggle to **Off**.
96+
97+
</TabItem> </Tabs>
98+
6599
:::note
66-
Turning off Page Shield will not turn off [policies](/page-shield/policies/). To turn off policies, go to **Page Shield** > **Policies**.
100+
101+
Turning off Page Shield's client-side resource monitoring will not turn off [policies](/page-shield/policies/). To turn off policies:
102+
103+
- Old dashboard: Go to **Security** > **Page Shield** > **Policies**.
104+
- New security dashboard: Go to **Security** > **Security rules** and filter by `Content security rules`.
105+
67106
:::

0 commit comments

Comments
 (0)