Xc testdrive july2025

docs/class2/lab1.rst

@@ -140,7 +140,7 @@ configuration.
 
 #. Under **Enforcement Mode**, change the mode to **Blocking**.
 
-#. In the **Detection Settings** section, click the **Security Policy**
+#. In the **Security Policy Settings** section, click the **Security Policy**
    dropdown.
 
 #. Select **Custom** from the dropdown menu. Additional configurations will
@@ -158,7 +158,7 @@ configuration.
    |lab015|
 
 #. Leaving all other values as default, scroll to the bottom and click
-   **Continue**.
+   **Add App Firewall**.
 
    |lab016|
 
@@ -176,7 +176,7 @@ configuration.
    left-hand navigation) to the **Other Settings** section and note the **VIP
    Advertisement** setting.
 
-#. Click **Save and Exit** at the bottom of the **HTTP Load Balancer**
+#. Click **Save HTTP Load Balancer** at the bottom of the **HTTP Load Balancer**
    configuration screen.
 
    |lab017|
@@ -343,7 +343,7 @@ configuration changes.
 
    |lab036|
 
-#. Expand your latest security event as shown.
+#. Expand your latest security event by clicking **Events** (may appear as just an **E**) in the upper-left.
 
    |lab036|
 
@@ -452,7 +452,7 @@ also further customize the WAF policy just built.
    .. note::
       *This allows for policy reuse and reduces the need for specific application WAF Policies*.
 
-#. Click on the **Cancel and Exit** to return to the prior window.
+#. Click on **Close** to return to the prior window.
 
    |lab051|
 

docs/class2/lab2.rst

@@ -74,6 +74,10 @@ Cloud Console.
 #. Select **Security Analytics** from the horizontal navigation.
 
 #. Locate the most recent security event, which should be your curl request.
+
+   .. note:: *This request could take up to 5 minutes to show up in this page.
+      If you still don’t see it after that, run the curl command again.*
+
    Expand the security event as you have done in prior exercises to observe
    the "Suspicious" Bot reporting. Remember the setting for Suspicious Bot was
    set to *Report* from Step 6 above.
@@ -114,7 +118,7 @@ and understand its implementation.
 #. Enable developer tools (Chrome shown (use F12)) and click on the **Network**
    tab.
 
-#. Using the 3 bars/menu icon (top right), navigate to **Access** link.
+#. In the application window, under the 3 bars/menu icon (top right), navigate to **Access** link.
 
 #. In the resulting login screen use the following values to login and click
    **Submit**
@@ -129,7 +133,7 @@ and understand its implementation.
 #. In the Developer window, find the **POST** to **auth.php**. **You can also
    use the filter** to find **auth.php**. Select the respective line as shown.
 
-#. Select the **Request** tab in the payload window that appears and observe
+#. Select the **Payload** tab in the window that appears and observe
    that you only see limited form POST data (identity, token, & submit).
 
    |lab012|
@@ -224,7 +228,7 @@ and understand its implementation.
 #. Observe that the **Bot Defense Policy** is now configured.
 
 #. Click **Other Settings** in the left-hand navigation or scroll to the
-   bottom on the **HTTP Load Balancer** screen, and click **Save and Exit**.
+   bottom on the **HTTP Load Balancer** screen, and click **Save HTTP Load Balancer**.
 
    |lab024|
 

docs/class2/lab3.rst

@@ -69,7 +69,7 @@ malicious user mitigation and actions.
 #. Review the two **User Identification Rules** and click **Apply**.
 
 #. Returning to the **User Identification** window, note that **User
-   Identification Rules** are now **Configured** and click **Continue**.
+   Identification Rules** are now **Configured** and click **Apply**, then **Save User Identification**.
 
    |lab010|
 
@@ -157,13 +157,13 @@ challenge.
 
    |lab021|
 
-#. Observe the three Rules created and select **Continue**.
+#. Observe the three Rules created and select **Add Malicious User Mitigation**.
 
    |lab022|
 
 #. Note the updated **Malicious User Mitigation and Challenges** section and
    click on **Other Settings** in the left-hand navigation or scroll to the
-   bottom of the window and click the **Save and Exit** button.
+   bottom of the window and click the **Save HTTP Load Balancer** button.
 
    |lab023|