Skip to content

[Page Shield] Clarify where sampling occurs #21363

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 2 commits into from
Apr 3, 2025
Merged

[Page Shield] Clarify where sampling occurs #21363

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
95b6b95
[Page Shield] Clarify where sampling occurs
pedrosousa Apr 3, 2025
1d992dd
Add link
pedrosousa Apr 3, 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
2 changes: 1 addition & 1 deletion src/content/docs/page-shield/how-it-works/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Enabling Page Shield adds a <GlossaryTooltip term="content security policy (CSP)

The **Monitors** dashboard shows the list of active scripts, connections, and cookies. The **All Reported Scripts** and **All Reported Connections** dashboards show the full list of detected scripts and connections in your domain, respectively, including infrequent and inactive ones.

Since Page Shield monitoring is based on sampling, there may be a small delay between deploying a script or cookie and having its data displayed in Page Shield's dashboards.
Page Shield adds a CSP report-only HTTP header used to monitor webpage resources to a sample of sent responses. This means that there may be a [small delay](/page-shield/troubleshooting/#why-do-i-not-see-scripts-after-i-activated-page-shield) between deploying a script or cookie and having its data displayed in Page Shield's dashboards.

Enterprise customers with a paid add-on have access to additional classification mechanisms based on threat feeds to determine if a script, or a connection made by a script, is malicious. For more information, refer to [Malicious script and connection detection](/page-shield/how-it-works/malicious-script-detection/).

Expand Down
2 changes: 1 addition & 1 deletion src/content/docs/page-shield/reference/csp-header.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ content-security-policy-report-only: script-src 'none'; connect-src 'none'; repo

:::note[Notes]

Cloudflare adds the CSP report-only HTTP header used to monitor webpages resources to a sample of sent responses.
Cloudflare adds the CSP report-only HTTP header used to monitor webpage resources to a sample of sent responses.

Configuring [log policies](/page-shield/policies/) will add other CSP report-only headers to responses. Cloudflare will not perform any sampling for these report-only headers related to customer-defined policies.

Expand Down
Loading