[Page Shield] Add new nav instructions (#23555)

Author: pedrosousa

src/content/docs/page-shield/alerts/alert-types.mdx

@@ -8,7 +8,7 @@ sidebar:
 
 import { AvailableNotifications } from "~/components";
 
-You can configure alerts for resources detected in your domain. Refer to [Page Shield alerts](/page-shield/alerts/) for more information.
+You can configure alerts for resources detected in your domain. Refer to [Alerts](/page-shield/alerts/) for more information.
 
 ## New resource alerts
 

src/content/docs/page-shield/alerts/configure.mdx

@@ -1,10 +1,10 @@
 ---
-title: Configure a Page Shield alert
+title: Configure an alert
 pcx_content_type: how-to
 sidebar:
   order: 2
   label: Configure an alert
-description: Configure scoped or unscoped Page Shield alerts to get notified about relevant client-side changes on your zones.
+description: Configure scoped or unscoped client-side resource alerts to get notified about relevant client-side changes on your zones.
 ---
 
 import { Render } from "~/components";

src/content/docs/page-shield/alerts/index.mdx

@@ -1,12 +1,12 @@
 ---
-title: Page Shield alerts
+title: Alerts
 pcx_content_type: concept
 sidebar:
   order: 5
   group:
     label: Alerting
-description: Page Shield alerts notify you when new scripts are detected
-  on your domain or when Page Shield detects resources that are likely
+description: Cloudflare client-side resource alerts notify you when new scripts
+  are detected on your domain or when Cloudflare detects resources that are likely
   malicious.
 ---
 
@@ -30,7 +30,7 @@ You can configure unscoped or scoped alerts:
 
 For alerts sent at regular intervals, you might experience a delay between adding a new script and receiving an alert.
 
-For instructions on configuring alerts, refer to [Configure a Page Shield alert](/page-shield/alerts/configure/).
+For instructions on configuring alerts, refer to [Configure an alert](/page-shield/alerts/configure/).
 
 ## Scoped alerts
 
@@ -42,11 +42,11 @@ If you have configured [allow policies](/page-shield/policies/#policy-actions) i
 
 When you create a scoped alert using the **Policies of these zones** alert filter, you will only receive the most relevant notifications based on the values of the allow policies you configured.
 
-For each scoped alert, Page Shield does the following:
+For each scoped alert, Cloudflare does the following:
 
 1. Check which allow policies in a zone are enabled.
 2. For every enabled policy, compare the URL of the new or changed resource against the allowed sources in the policy.
-3. If the resource is allowed by the policy, check if the new or modified resource should trigger the current Page Shield alert.
+3. If the resource is allowed by the policy, check if the new or modified resource should trigger the current alert.
 4. If the alert should trigger, send an alert notification to the configured destinations.
 
 When you create a scoped alert you will not receive notifications for resources blocked by an allow policy. These are [policy violations](/page-shield/policies/violations/) that you can review in the dashboard, through GraphQL, or via Logpush.

src/content/docs/page-shield/best-practices/handle-an-alert.mdx

@@ -1,24 +1,26 @@
 ---
-title: Handle a Page Shield alert
+title: Handle a client-side resource alert
 pcx_content_type: tutorial
-updated: 2023-03-23
+updated: 2025-06-13
 sidebar:
   order: 2
   label: Handle an alert
 ---
 
-If you receive a Page Shield alert, sometimes you need to perform some manual investigation to confirm the nature of the script. Use the guidance provided in this page as a starting point for your investigation.
+If you receive a client-side resource alert, sometimes you need to perform some manual investigation to confirm the nature of the script. Use the guidance provided in this page as a starting point for your investigation.
 
 ## 1. Understand what triggered the alert
 
-Start by identifying the [detection system](/page-shield/how-it-works/malicious-script-detection/) that triggered the alert. A link is provided in the alert that will send you directly to the Page Shield dashboard to the relevant resource that needs reviewing. Alternatively, do the following:
+Start by identifying the [detection system](/page-shield/how-it-works/malicious-script-detection/) that triggered the alert. A link is provided in the alert that will send you directly to the Cloudflare dashboard to the relevant resource that needs reviewing. Alternatively, do the following:
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
-2. Go to **Security** > **Page Shield**.
+2. Navigate to the client-side resource monitoring page:
+   - Old dashboard: Go to **Security** > **Page Shield**.
+   - New security dashboard: Go to **Security** > **Web assets** > **Client-side resources** tab.
 3. Select **Scripts** or **Connections** and search for the resource mentioned on the alert you received.
 4. Select **Details** next to the resource you identified. The example screenshot below shows a malicious script resource.
 
-![Page Shield dialog box showing the details of a script considered malicious.](~/assets/images/page-shield/handle-alert-malicious-script-example.png)
+![Dialog box showing the details of a script considered malicious.](~/assets/images/page-shield/handle-alert-malicious-script-example.png)
 
 The details page will specify which detection system triggered the alert. Check the values of the following fields:
 
@@ -58,11 +60,11 @@ In this case, in addition to the steps indicated below, the best approach is:
 
 ## 3. Check the script reputation
 
-If Page Shield considers the resource’s domain a "malicious domain", it is likely that the domain does not have a good reputation. The domain may be known for hosting malware or for being used for phishing attacks. Usually, reviewing the domain/hostname is sufficient to understand why you received the alert. You can use tools like Cloudflare's [Security Center Investigate](https://dash.cloudflare.com/?to=/:account/security-center/investigate) platform to help with this validation.
+If Cloudflare considers the resource’s domain a "malicious domain", it is likely that the domain does not have a good reputation. The domain may be known for hosting malware or for being used for phishing attacks. Usually, reviewing the domain/hostname is sufficient to understand why you received the alert. You can use tools like Cloudflare's [Security Center Investigate](https://dash.cloudflare.com/?to=/:account/security-center/investigate) platform to help with this validation.
 
 If Cloudflare's internal systems classified the script as containing "malicious code", external tools may not confirm the detection you got from Page Shield, since the machine learning (ML) model being used is Cloudflare-specific technology.
 
-If you believe that Page Shield's classification is a false positive, contact your account team so that we can further improve Page Shield's underlying technology.
+If you believe that Cloudflare's classification is a false positive, contact your account team so that we can further improve Page Shield's underlying technology.
 
 ## 4. (Optional) Analyze the script content
 
@@ -76,7 +78,7 @@ You could use a virtual machine to perform some of the following analysis:
 
 ## Conclusion
 
-If a resource which triggered a malicious alert from Page Shield:
+If a resource which triggered a malicious resource alert:
 
 - Is actively present in your application
 - Is being loaded from a malicious host or IP address, or has malicious code

src/content/docs/page-shield/best-practices/index.mdx

@@ -11,6 +11,6 @@ description: Best practices for using Page Shield.
 
 import { DirectoryListing } from "~/components";
 
-Review the topics below for best practices related to Page Shield:
+Review the topics below for best practices related to Page Shield's client-side resource monitoring:
 
 <DirectoryListing />

src/content/docs/page-shield/detection/monitor-connections-scripts.mdx

@@ -7,31 +7,32 @@ sidebar:
 
 import { Render } from "~/components";
 
-Once you [activate Page Shield](/page-shield/get-started/), the **Monitors** dashboard will show which resources (scripts and connections) are running on your domain, as well as the cookies recently detected in HTTP traffic.
+Once you [activate Page Shield's client-side resource monitoring](/page-shield/get-started/), the main client-side resources dashboard will show which resources (scripts and connections) are running on your domain, as well as the cookies recently detected in HTTP traffic.
 
 If you notice unexpected scripts or connections on the dashboard, check them for signs of malicious activity. Enterprise customers with a paid add-on will have their [connections and scripts classified as potentially malicious](/page-shield/how-it-works/malicious-script-detection/) based on threat feeds. You should also check for any new or unexpected cookies.
 
 :::note
 
-- Users in Free and Pro plans only have access to the script monitor.
-- If you recently activated Page Shield, you may see a delay in reporting.
+- Users in Free and Pro plans only have access to script monitoring.
+- If you recently activated client-side resource monitoring, you may see a delay in reporting.
 
 :::
 
-## Use the Monitors dashboard
+## Use the client-side resources dashboards
 
-To review the resources and cookies detected by Page Shield:
+To review the resources detected by Cloudflare:
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
 
-2. Go to **Security** > **Page Shield**.
+2. Go to the client-side resources page:
+   - Old dashboard: Go to **Security** > **Page Shield**.
+   - New security dashboard: Go to **Security** > **Web assets** > **Client-side resources** tab.
 
-3. Under **Monitors**, review the list of scripts, connections, and cookies for your domain. To apply a filter, select **Add filter** and use one or more of the available options:
-
-   - **Script**: Filter scripts by their URL.
-   - **Connection**: Filter connections by their target URL. Depending on your [configuration](/page-shield/reference/settings/#connection-target-details), it may search only by target hostname.
-   - **Host**: Look for scripts appearing on specific hostnames, or connections made in a specific hostname.
-   - **Page** (requires a Business or Enterprise plan): Look for scripts appearing in a specific page, or for connections made in a specific page. Searches the first page where the script was loaded (or where the connection was made) and the latest occurrences list.
+3. Review the list of scripts, connections, and cookies for your domain. To apply a filter, select **Add filter** and use one or more of the available options:
+   - **Script URL**: Filter scripts by their URL.
+   - **Connection URL**: Filter connections by their target URL. Depending on your [configuration](/page-shield/reference/settings/#connection-target-details), it may search only by target hostname.
+   - **Seen on host**: Look for scripts appearing on specific hostnames, or connections made in a specific hostname.
+   - **Seen on page** (requires a Business or Enterprise plan): Look for scripts appearing in a specific page, or for connections made in a specific page. Searches the first page where the script was loaded (or where the connection was made) and the latest occurrences list.
    - **Status**: Filter scripts or connections by [status](/page-shield/reference/script-statuses/).
    - **Type**: Filter cookies according to their type: first-party cookies or unknown.
    - Cookie property: Filter by a cookie property such as **Name**, **Domain**, **Path**, **Same site**, **HTTP only**, and **Secure**.
@@ -40,12 +41,15 @@ To review the resources and cookies detected by Page Shield:
 
 ## View all reported scripts or connections
 
-The All Reported Connections and All Reported Scripts dashboards show all the detected resources including infrequent or inactive ones, reported in the last 30 days. After 30 days without any report, Page Shield will delete information about a previously reported resource, and it will no longer appear in any of the dashboards.
+The All Reported Connections and All Reported Scripts dashboards show all the detected resources including infrequent or inactive ones, reported in the last 30 days. After 30 days without any report, Cloudflare will delete information about a previously reported resource, and it will no longer appear in any of the dashboards.
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
-2. Go to **Security** > **Page Shield** > **Monitors**.
+2. Go to the client-side resources page:
+   - Old dashboard: Go to **Security** > **Page Shield**.
+   - New security dashboard: Go to **Security** > **Web assets** > **Client-side resources** tab.
+
 3. Select **Scripts** or **Connections**.
-4. Select **View all**.
+4. Select **View all scripts** or **View all connections**.
 5. Review the information displayed in the dashboard.
 
 You can filter the data in these dashboards using different criteria, and print a report with the displayed records.
@@ -77,7 +81,6 @@ The script details also include the last 10 script versions detected by Page Shi
 The details of each cookie include:
 
 - **Type**: A cookie can have the following types:
-
   - **First-party**: Cookies set by the origin server through a `set-cookie` HTTP response header.
   - **Unknown**: All other detected cookies.
 
@@ -113,6 +116,11 @@ Use this feature to extract data from Page Shield that you can review and annota
 
 To export script, connection, or cookie information in CSV format:
 
-1. Go to the **Monitors** tab and select **Scripts**, **Connections**, or **Cookies**.
-2. (Optional) Apply any filters to the displayed data.
-3. Select **Download CSV**.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
+2. Go to the client-side resources page:
+   - Old dashboard: Go to **Security** > **Page Shield**.
+   - New security dashboard: Go to **Security** > **Web assets** > **Client-side resources** tab.
+
+3. Select **Scripts**, **Connections**, or **Cookies**.
+4. (Optional) Apply any filters to the displayed data.
+5. Select **Download CSV**.

src/content/docs/page-shield/detection/review-changed-scripts.mdx

@@ -11,12 +11,16 @@ description: Learn how to review scripts on your domain after receiving a code c
 Available as a paid add-on for customers on an Enterprise plan.
 :::
 
-Page Shield analyzes the JavaScript dependencies in the pages of your domain over time.
+Cloudflare analyzes the JavaScript dependencies in the pages of your domain over time.
 
 You can configure a notification for [code change alerts](/page-shield/alerts/alert-types/#code-change-alert) to receive a daily notification about changed scripts in your domain.
 
 When you receive such a notification:
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
-2. Go to **Security** > **Page Shield** > **Monitors**.
+2. Go to the client-side resources page:
+
+   - Old dashboard: Go to **Security** > **Page Shield**.
+   - New security dashboard: Go to **Security** > **Web assets** > **Client-side resources** tab.
+
 3. Check the details of each changed script and validate if it is an expected change.