> For the complete documentation index, see [llms.txt](https://waf-doc.inext.checkpoint.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://waf-doc.inext.checkpoint.com/additional-security-engines/anti-bot-challenge-rules.md).
# Anti-Bot Challenge Rules
### Overview
Anti-Bot rules allow you to **Detect, Challenge, or Prevent** traffic that matches specific criteria in order to mitigate automated abuse such as:
* Credential stuffing
* Brute-force attacks
* Account enumeration
* Bot Driven DDoS
#### Action Modes
* **Detect** – Logs matching traffic only.\
*Recommended first step to validate impact before enforcement.*
* **Challenge (captcha)** – Requires the client to pass a browser challenge before access is granted.\
Use to stop automation while allowing legitimate users.
* **Prevent** – Blocks matching requests.\
Use after validation or during active attacks.
**Best practice:** Start with **Detect**, then move to **Challenge**
### How to Configure Anti Bot Rules
#### Add Rules
1. Navigate to **Anti-Bot Tab → Challenge Rules SubPractice → Add Rule**
1. Select the desired **Action** (Detect, Challenge, or Prevent).
2. Enter the target **URI** (e.g., `/login`).
3. (Optional) Add **Additional Conditions** to narrow the scope.\
You may choose one of the following:
* Source Identifier
* Source IP
* URI
* Country Code
* Country Name
4. Save the rule.
#### Add a Captcha Challenge
1. Navigate to the "Behaviors" Tab and create a new captcha object
2. Configure the Captcha object that will be used when a rule triggers a challenge:
* **Name**: Enter a friendly name for the Captcha object, or keep the default.
* **Captcha Type**: Select the challenge mechanism. *(Currently set by default to **Proof of Work**.)*
* **TTL**: The time-to-live (in minutes) for the successful challenge. During this period, the user will not be required to complete a new challenge.
* **Message Title (optional)**: The title shown on the challenge HTML page presented to the end user.
* **Message Body (optional)**: The text displayed on the challenge HTML page presented to the end user.
Example of a page challenge page displayed to the user
3. Connect the Captcha object to the practice:
2. Enforce policy
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://waf-doc.inext.checkpoint.com/additional-security-engines/anti-bot-challenge-rules.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
