---
title: Serving challenges with interstitial pages
summary: null
url: >-
  https://www.fastly.com/documentation/guides/security/client-challenges/serving-challenges-with-interstitial-pages
---

> **IMPORTANT:** This guide only applies to customers who have deployed [Bot Management](https://docs.fastly.com/products/bot-management) with post-cache inspection. If you've deployed Bot Management with pre-cache inspection (ContentGuard) or are using Fastly DDoS Protection, check out our [Getting started with client challenges](https://www.fastly.com/documentation/guides/security/client-challenges/getting-started-with-client-challenges) guide instead.

With interstitial pages, you can deploy client challenges without touching your application code. Fastly serves a temporary page to run the challenge before loading the requested content. All configuration happens in the control panel, and you can choose from dynamic, non-interactive, and interactive challenge types.

> **HINT:** Have a React or single-page application? Embed a [dynamic challenge](https://www.fastly.com/documentation/guides/security/client-challenges/embedding-dynamic-challenges-in-pages) within your web application. React and single-page applications don't handle interstitial pages well.

## Prerequisites

Before setting up client challenges, you must [deploy Bot Management](https://www.fastly.com/documentation/guides/security/bot-management/about-bot-management/#deploying-bot-management) using post-cache inspection on each CDN service where you intend to use them. Compute services are not supported.

## Adding challenges

To serve a challenge on an interstitial page, complete the following steps:

### Fastly Control Panel

1.   Log in to the [Fastly control panel](https://manage.fastly.com).

2.   Go to **Security** > **Next-Gen WAF** > [**Rules**](https://manage.fastly.com/security/ngwaf/rules).

3.   From the workspaces bar, click the menu <span class="inline-icons"><img src="https://www.fastly.com/documentation/img/icons/chevron-down.png" alt="Menu icon" /></span> to the right of the workspace name and select a workspace.

4. Click **Add workspace rule**.

5. In the **Type** area, select **Request** to challenge all requests matching your conditions or **Rate limit** to challenge requests only when they exceed a defined threshold. For more information, check out our [About rules](https://www.fastly.com/documentation/guides/next-gen-waf/rules/about-rules) guides.

6. In the **Conditions** area, define where the rule should send the challenge. For example, to send a challenge to all request traffic destined for `www.example.com/login`, create the following conditions:

   | Condition | Field  | Operator | Value             |
   | --------- | ------ | -------- | ----------------- |
   | 1         | Method | Equals   | GET               |
   | 2         | Domain | Equals   | `www.example.com` |
   | 3         | Path   | Equals   | `/login`          |

7. _(Optional)_ In the **Conditions area**, add conditions to restrict when the rule should send the challenge. For example, if you don't want to send challenges to requests with the `VERIFIED-BOT` signal, add the following condition:

   - From the first **Field** menu, select **Signal**.
   - From the first **Operator** menu, select **Does not exist where**.
   - Select **All** to specify that a request must meet every condition.
   - From the second **Field** menu, select **Signal ID**.
   - From the second **Operator** menu, select **Equals**.
   - From the **Value** menu, select **Verified Bot**.

   In the Fastly control panel, the settings would appear like this:

   ![Verified bots condition group](https://www.fastly.com/documentation/img/ngwaf/verified-bot-condition-fcp.png)

8. In the **Actions** area, define the [type of challenge](https://www.fastly.com/documentation/guides/security/client-challenges/how-client-challenges-work/#challenge-types) the rule should send.

   | Challenge type            | Actions area                                                                                                                                                                                                 |
   | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
   | Dynamic challenge         | From the **Action type** menu, select [**Dynamic challenge**](https://www.fastly.com/documentation/guides/next-gen-waf/rules/about-rules/#action-types).                                                     |
   | Non-interactive challenge | From the **Action type** menu, select [**Browser challenge**](https://www.fastly.com/documentation/guides/next-gen-waf/rules/about-rules/#action-types) and leave the **Allow Interactive** switch disabled. |
   | Interactive challenge     | From the **Action type** menu, select [**Browser challenge**](https://www.fastly.com/documentation/guides/next-gen-waf/rules/about-rules/#action-types) and enable the **Allow Interactive** switch.         |

9. Fill out the fields in the **Details** area as follows:
   - In the **Description** field, enter a description for the rule.
   - Leave the **Status** switch for the rule enabled.

10. Click **Create workspace rule**.

### Next Gen Waf Control Panel

1.   Log in to the [Next-Gen WAF control panel](https://dashboard.signalsciences.net).

2.   From the **Sites** menu, select a site if you have more than one site.

3. From the **Rules** menu, select **Site Rules**.

4. Click **Add site rule**.

5. In the **Type** area, select **Request** or **Rate limit**. For information about each [rule type](https://www.fastly.com/documentation/guides/next-gen-waf/rules/about-rules/#rule-types), check out our [Working with request rules](https://www.fastly.com/documentation/guides/next-gen-waf/rules/working-with-request-rules) and [Working with advanced rate limiting rules](https://www.fastly.com/documentation/guides/next-gen-waf/rules/working-with-advanced-rate-limiting-rules) guides.

6. In the **Conditions** area, define where the rule should send the challenge. For example, to send a challenge to all request traffic destined for `www.example.com/login`, create the following conditions:

   | Condition | Field  | Operator | Value             |
   | --------- | ------ | -------- | ----------------- |
   | 1         | Method | Equals   | GET               |
   | 2         | Domain | Equals   | `www.example.com` |
   | 3         | Path   | Equals   | `/login`          |

7. _(Optional)_ In the **Conditions area**, add conditions to restrict when the rule should send the challenge. For example, if you don't want to send challenges to requests with the `VERIFIED-BOT` signal, add the following condition:

   - From the first **Field** menu, select **Signal**.
   - From the first **Operator** menu, select **Does not exist where**.
   - Select **All** to specify that a request must meet every condition.
   - From the second **Field** menu, select **Signal Type**.
   - From the second **Operator** menu, select **Equals**.
   - From the **Value** menu, select **Verified Bot**.

   In the Next-Gen WAF control panel, the settings would appear like this:

   ![Verified bots condition group](https://www.fastly.com/documentation/img/ngwaf/verified-bot-condition-group.png)

8. In the **Actions** area, define the [type of challenge](https://www.fastly.com/documentation/guides/security/client-challenges/how-client-challenges-work/#challenge-types) the rule should send.

   | Challenge type            | Actions area                                                                                                                                                                                                 |
   | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
   | Dynamic challenge         | From the **Action type** menu, select [**Dynamic challenge**](https://www.fastly.com/documentation/guides/next-gen-waf/rules/about-rules/#action-types).                                                     |
   | Non-interactive challenge | From the **Action type** menu, select [**Browser challenge**](https://www.fastly.com/documentation/guides/next-gen-waf/rules/about-rules/#action-types) and leave the **Allow Interactive** switch disabled. |
   | Interactive challenge     | From the **Action type** menu, select [**Browser challenge**](https://www.fastly.com/documentation/guides/next-gen-waf/rules/about-rules/#action-types) and enable the **Allow Interactive** switch.         |

9. Fill out the fields in the **Details** area as follows:
   - In the **Description** field, enter a description for the rule.
   - Leave the **Status** switch for the rule enabled.

10. Click **Create site rule**.

After adding a challenge, you can optionally:

- [Add a custom logo](https://www.fastly.com/documentation/guides/security/client-challenges/adding-custom-logos-to-interstitial-pages) to the interstitial page where the challenge is served.
- [Set up rules](https://www.fastly.com/documentation/guides/security/client-challenges/blocking-requests-with-invalid-challenge-tokens) to block requests from clients that failed a challenge.

## Related content

- [Getting started with client challenges](https://www.fastly.com/documentation/guides/security/client-challenges/getting-started-with-client-challenges)
- [Blocking requests with invalid tokens](https://www.fastly.com/documentation/guides/security/client-challenges/blocking-requests-with-invalid-challenge-tokens)
- [Adding custom logos to interstitial pages](https://www.fastly.com/documentation/guides/security/client-challenges/adding-custom-logos-to-interstitial-pages)
