About post-cache inspection

When Bot Management is deployed using post-cache inspection, Bot Management works alongside the Next-Gen WAF to analyze cache-miss requests, protecting your origin from bot attacks. This means that Bot Management only inspects traffic going to your origin.

Prerequisites

Before configuring Bot Management and monitoring your bot traffic, you must:

Quick start

After deploying Bot Management using post-cache inspection, Fastly immediately starts analyzing your traffic for bot activity and logging results. You can then:

  • monitor and manage your bot traffic
  • add client challenges
  • add detection for headless bots

Monitor and manage bot traffic

  1. Fastly control panel
  2. Next-Gen WAF control panel
  1. Log in to the Fastly control panel.
  2. Go to Security > Next-Gen WAF > Dashboards.
  3. From the workspaces bar, click the menu Menu icon to the right of the workspace name and select a workspace.
  4. From the dashboards menu Menu icon, select Bot Management.
  5. Monitor the suspected bot activity and bot-related signals detected by the Next-Gen WAF.
  6. Create rules to control bot access to your web application. For example, you can add a rule to block suspected bad bots.

Add client challenges

Client challenges are security tasks that verify users are human or accessing your web application through a legitimate browser. To minimize disruption to your application's user experience, you can configure these challenges to run invisibly in the background using non-interactive methods (e.g., JavaScript proof-of-work) and only present interactive challenges (e.g., CAPTCHA) when suspicious activity is detected. Alternatively, you can choose to serve only non-interactive or interactive challenges.

To add a challenge, complete the following steps:

  1. Select the type of challenge you'd like to send and set it up.

    Challenge typeServed on an interstitial pageEmbedded within a page
    Dynamic challengeCreate a rule with the Dynamic challenge action.Modify the HTML of the page where you'd like to embed the challenge.
    Non-interactive challengeCreate a rule with the Browser challenge action and the Allow Interactive switch disabled.Not supported.
    Interactive challengeCreate a rule with the Browser challenge action and the Allow Interactive switch enabled.Not supported.

    HINT: Have a React or single-page application? Embed a dynamic challenge within your web application. React and single-page applications don't handle interstitial pages well.

  2. Add rules to validate challenge tokens and block requests with invalid tokens.

For quick start instructions on how to add client challenges, check out our Getting started guide.

Add detection for headless bots

By default, Bot Management doesn't detect bots that leverage headless browsers (e.g., headless Chrome). You can optionally extend detection for headless bots by adding the following line within the <head> section of your HTML. This sets up the Advanced client-side detection feature.

<script src="/_fs-ch-1T1wmsGaOgGaSxcX/assets/script.js"></script>