Skip to content

Commit ff72439

Browse files
authored
[Page Shield] Update troubleshooting (#22052)
1 parent 9849512 commit ff72439

File tree

2 files changed

+9
-13
lines changed

2 files changed

+9
-13
lines changed

src/content/docs/page-shield/how-it-works/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Enabling Page Shield adds a <GlossaryTooltip term="content security policy (CSP)
1818

1919
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.
2020

21-
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.
21+
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/#page-shield-does-not-show-any-resources-after-activating-it) between deploying a script or cookie and having its data displayed in Page Shield's dashboards.
2222

2323
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/).
2424

src/content/docs/page-shield/troubleshooting.mdx

Lines changed: 8 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -8,17 +8,21 @@ sidebar:
88

99
import { GlossaryTooltip } from "~/components";
1010

11-
## Why do I not see scripts after I activated Page Shield?
11+
### How do I set up Page Shield?
12+
13+
For help setting up Page Shield, refer to our [get started guide](/page-shield/get-started/).
14+
15+
## Page Shield does not show any resources after activating it
1216

1317
Page Shield does not collect data on every single page view. Instead, it uses a sampling approach to gather information efficiently. This means that domains with lower traffic might take longer to generate initial reports, as these domains need more page views to accumulate enough samples. To speed up the reporting process, it is recommended that you actively generate traffic to your application after [activating Page Shield](/page-shield/get-started/). This will provide Page Shield with more data to work with, leading to faster report generation.
1418

15-
## Why do I see scripts that I do not recognize?
19+
## Page Shield shows scripts and connections that I do not recognize
1620

1721
Scripts often reference other scripts outside your application.
1822

1923
But, if you see unexpected scripts on your Script Monitor dashboard, check them for signs of malicious activity.
2024

21-
## Why do I see warnings in my browser's developer tools related to Content Security Policy (CSP)?
25+
## I get warnings in my browser's developer tools related to Content Security Policy (CSP)
2226

2327
Page Shield uses a <GlossaryTooltip term="content security policy (CSP)">Content Security Policy (CSP)</GlossaryTooltip> report-only directive to gather a list of all scripts running on your application.
2428

@@ -34,7 +38,7 @@ is required to enable inline execution.
3438

3539
You can safely ignore these warnings, since they are related to the reports that Page Shield requires to detect loaded scripts. For more information, refer to [How Page Shield works](/page-shield/how-it-works/).
3640

37-
## Why do I get policy violation reports for a domain I allowlisted?
41+
## I get policy violation reports for a domain I allowlisted
3842

3943
Policy violations reported via CSP's [report-only directive](/page-shield/reference/csp-header/) do not take into consideration any redirects or redirect HTTP status codes. This is [by design](https://www.w3.org/TR/CSP3/#create-violation-for-request) for security reasons.
4044

@@ -43,11 +47,3 @@ Some third-party services you may want to cover in your Page Shield allow polici
4347
For example, if you add the `adservice.google.com` domain to an allow policy, you could get policy violation reports for this domain due to redirects to a different domain (not present in your allow policy). In this case, the violation report would still mention the original domain, and not the domain of the redirected destination, which can cause some confusion.
4448

4549
To try to solve this issue, add the domain of the redirected destination to your allow policy. You may need to add several domains to your policy due to redirects.
46-
47-
## Do I have access to Page Shield?
48-
49-
Yes, Page Shield is available on all plans. For details on the available features per plan, refer to [Availability](/page-shield/#availability).
50-
51-
### How do I set up Page Shield?
52-
53-
For help setting up Page Shield, refer to our [get started guide](/page-shield/get-started/).

0 commit comments

Comments
 (0)