Bot Manager Standard

Use bot manager to require a client (e.g., a web browser) to solve a challenge before resolving the request. WAF blocks traffic when the client cannot solve this challenge within a few seconds. Basic bots typically cannot solve this type of challenge and therefore their traffic is blocked. This prevents them from scraping your siteRefers to harvesting data from your site., cardingRefers to the process through which stolen credit cards are authorized., spamming your forms, launching DDoS attacks, and committing ad fraud.

Solving a challenge requires a JavaScript-enabled client. Users that have disabled JavaScript on their browsing session will be unable to access content protected by bot rules.

We strongly recommend that you avoid applying bot rules to machine-to-machine interactions. For example, applying bot rules to API traffic will disrupt your API workflow.

How Does It Work?

Content protected by bot rules undergoes the following workflow:

1. Browser Challenge

   WAF sends a browser challenge in response to requests for content protected by bot rules. It is up to the client to solve this challenge within a few seconds.

2. Response

   The results of the above browser challenge determines what happens next.

   • Solved: If the client is able to solve the challenge, then our CDN serves the requested content. Additionally, a cookie will be added to the user's session. This cookie instructs our CDN to serve content to the user without requiring a browser challenge. Once the cookie expires, new requests for content protected by bot rules will once again require the client to solve a challenge.

     Define the duration for this cookie through the Valid for (in minutes) option when setting up the enforcement of bot rules within your Security Application Manager configuration.

   • Unsolved: If the client is unable to solve the challenge, then our CDN responds with a new browser challenge.

Bot Manager Configuration

A Bot Manager configuration set defines the set of requests that will be protected by bot rules. Each rule contains:

• Up to 6 conditions that define request identification criteria.

• A rule ID and message that will be associated with requests identified by this rule.

  Assigning a unique ID and message to each rule makes it easy to identify requests detected as a result of a specific rule.

  A rule ID must be a number between 77,000,000 and 77,999,999.

A Bot Manager configuration may contain up to 10 rules.

Request Identification

WAF identifies a request when it satisfies at least one rule in a Bot Manager configuration. The manner in which a rule is satisfied varies by type.

• Custom Matches: This type of rule is satisfied when a match is found for each of its conditions. A condition determines request identification by defining what will be matched (i.e., variable), how it will be matched (i.e., operator), and a match value.

  Certain variables match on key-value pairs. If you match on multiple keys within a single variable, WAF will only need to find one of those matches to satisfy that variable.
  
  For example, if you set up a request header variable to match for Authorization and Content-Type, then requests that contain either or both of those headers will satisfy that variable.

• Edgecast Reputation DB: This type of rule is satisfied when the client's IP address matches an IP address defined within our reputation database. Our reputation database contains a list of IP addresses known to be used by bots.

Conditions

A condition determines how requests will be identified through variables, operators, match values, and negative matching.

Variables

A variable identifies the request element that WAF will analyze. We support the following request elements:

• ASN: Identifies requests by the Autonomous System Number (ASN) associated with the client's IP address.

  Specify a regular expression to match for multiple ASNs.
  Example: 
  Use the following pattern to match for requests from either 15133 or 14153:
  15133|14153

• Country: Identifies requests by the country from which the request originated. Specify the desired country using a country code.

  Specify a regular expression to match for multiple country codes.
  Example: 
  Use the following pattern to match for requests from the United States, Canada, or Mexico:
  US|CA|MX

• IP address: Identify requests by the requester's IP address. Specify a comma-delimited list of the desired IP address(es) using standard IPv4/IPv6 and CIDR notation. Specify a subnet by appending a slash (/) and the desired bit-length of the prefix (e.g., 11.22.33.0/22). Do not specify more than 1,000 IP addresses or IP blocks.

  Example:

  192.0.2.20,203.0.113.0/24,2001:DB8::/32

• Request cookies: Match against all or specific cookies.

  • All: Do not specify the desired cookie within this variable and specify the desired cookie value or pattern within the Match value option.

  • Specific Cookies: Define the name of the desired cookie within this variable and specify the desired cookie value or pattern within the Match value option.

    Setting up a cookie variable also allows you to define whether WAF uses a regular expression, a negative match, or both when comparing the value assigned to the variable against cookies. Use a negative match to find requests whose payload does not contain the specified cookie.

• Request header: Match against all or specific request headers.

  • All: Do not specify the desired request header within this variable and specify the desired header value or pattern within the Match value option.

  • Specific Request Headers: Define the name of the desired request header within this variable and specify the desired header value or pattern within the Match value option.

    Setting up a request header variable also allows you to define whether WAF uses a regular expression, a negative match, or both when comparing the value assigned to the variable against request headers. Use a negative match to find requests whose payload does not contain the specified request header.

• Request method: Match against request method (e.g., GET and POST).

• Request query: Match against the request's query string. Specify the desired value or pattern within the Match value option.

• Request URI: Match against the request's URL path and query string. Define a URL path that starts directly after the hostname. Exclude the protocol and hostname when defining this property.

  WAF does not transform edge CNAME URLs to CDN URLs prior to performing this comparison.

  Sample values:

  /marketing?id=123456

  /resources/images

• Request URL path: Match against the request's URL path. Define a URL path that starts directly after the hostname. Exclude the protocol, hostname, and query string when defining this property.

  Our service does not transform edge CNAME URLs to CDN URLs prior to performing this comparison.

  Sample values:

  /marketing

  /resources/images

All variables support the ability to match on the number of times that a request element is found within the request. Set up a variable to match on the number of instances instead of inspecting the element for a specific value or regular expression pattern by marking the Count option.

You may define zero or more keys when setting up variables that match on key-value pairs. WAF must find at least one of the specified keys in the request before that variable will be satisfied. For example, if you set up a request header variable to match for Authorization and Content-Type, then requests that contain either or both of those headers will satisfy that variable.

Operators

An operator determines how WAF will compare a match value against the request element identified by a variable.

• Begins with: A match is found when the request element starts with the specified match value.
• Contains: A match is found when the request element contains the specified match value.
• Ends with:  A match is found when the request element ends with the specified match value.

• Exact match:  A match is found when the request element is an exact match to the specified match value.

  Avoid enabling the Negative match option with the Exact match operator. This configuration will not yield the expected set of matches.

• Regex: A match is found when the request element satisfies the regular expression defined in the match value.

• Value match: A match is found when the request element occurs the exact number of times defined in the match value.

  The Value match operator should only be used when the Count option has been enabled.

Match Value

WAF uses a match value to identify threats.

• Default: By default, WAF compares a match value against the request element identified by a variable (e.g., URL path or a request header's value).
• Count: Enable the Count option on a variable to compare this value against the number of times that the request element identified by a variable (e.g., a specific cookie or request header) occurs within the request.

Example:

This example assumes the following configuration:

We will now examine how the Count option affects comparisons for this configuration.

• Disabled: If the Count option has been disabled on the variable, then WAF will compare the value of the Authentication request header to 1.
• Enabled: If the Count option has been enabled on the variable, then WAF will compare the number of times that the Authentication request header occurred in the request to 1.

The type of comparison that will be performed is determined by the Operator option.

Bot Manager Configuration Administration

You may create, modify, and delete Bot Manager configurations.

Key information:

• Administer Bot Manager configuration from the Bot Manager page.
• Apply a Bot Manager configuration to production traffic by adding it to a Security Application Manager configuration. Multiple Security Application Manager configurations may use the same Bot Manager configuration. Leverage this capability to tailor security screening by application or traffic profile.
• It may take up to 2 minutes for an updated Bot Manager configuration to be applied across our entire network.

To create a Bot Manager configuration

1. Navigate to the Bot Manager page. How?From the main menu, navigate to More | Security | WAF Tier | Security Rule Manager | Bot Manager.

2. Click Add Bot Rule.
3. In the Name option, type the unique name by which this Bot Manager configuration will be identified. This name should be sufficiently descriptive to identify it when setting up a Security Application Manager configuration.
4. Determine whether to serve a custom browser challenge through the Custom browser challenge option. If you mark this option, then you will need to set the Response body option to your custom browser challenge.
5. From the Valid for (in minutes) option, type the number of minutes for which our CDN will serve content to a client that solves a browser challenge without requiring an additional browser challenge to be solved. Specify a value between 1 and 1,440 minutes.
6. From the HTTP status code option, determine the HTTP status code for the response provided to clients that are being served the browser challenge.

7. Create a rule that identifies the set of traffic that will be served a browser challenge.

   1. From the Rules tab, click + Add Rule.

   2. In the Rule type option, select the type of rule that will be created.

      • Custom Matches: This type of rule is satisfied when a match is found for each of its conditions.

        1. In the Name option, type a name that identifies the purpose of this rule.
        2. In the Rule ID option, specify a number between 77,000,000 and 77,999,999.
        3. In the Rule message option, type a brief description for this rule.

        4. A custom matches rule automatically includes a default condition. Modify this condition to determine how WAF will identify requests. From the condition's Variable option, select the request element through which WAF will identify requests.

           Learn more about variables.

        5. Certain variables (e.g., request cookies and request header) match on name and value. If you have selected this type of variable, then perform the following steps:

           1. Click + Add Match.

           2. From the Name option, type the desired name.

              For example, match for requests that contain an Authorization header by setting this option to Authorization.

           3. Optional. Mark the Negative Match option to match for requests that do not contain a matching value for the name defined in the previous step.
           4. If you specified a regular expression in the Name option, then you should mark the Regex Match option.
           5. Optional. Add another match through which this variable can be satisfied by repeating steps a - d.

        6. Optional. Mark the Count option to match by the number of instances that a match is found instead of by inspecting that request element.

           Learn more.

        7. From the Operator option, select an operator that determines how WAF will compare the match value to the request element identified by the above variable.

           Learn more.

        8. In the Match value option, type the value that will be compared against the request element identified by the above variable.
        9. Optional. Mark the Negative Match option to match for requests that do not contain a matching value for the value defined in step vi.
        10. Optional. Click + Add Condition to add another condition that must be met prior to request identification. Repeat steps i - ix for this new condition.
      • Edgecast Reputation DB: This type of rule is satisfied when the client's IP address matches an IP address within our reputation database. Proceed to the next step.
8. Optional. Click + Add Rule to add another rule through which WAF may identify requests. Repeat step 7.
9. Click Save.

To modify a Bot Manager configuration

1. Navigate to the Bot Manager page. How?From the main menu, navigate to More | Security | WAF Tier | Security Rule Manager | Bot Manager.

2. Click on the desired Bot Manager configuration.

3. Make the desired changes.

   Key tasks:

   • Change the type of rule from the Rule type option.

   • Custom matches only

     Delete variables and matches within a variable by clicking .

   • Custom matches only

     Delete a condition by clicking Delete Condition.

     A rule must have at least one condition. Therefore, you cannot delete the root condition.

   • Delete a rule by clicking Delete Rule and then clicking Confirm.
4. Click Save.

To delete a Bot Manager configuration

1. Navigate to the Bot Manager page. How?From the main menu, navigate to More | Security | WAF Tier | Security Rule Manager | Bot Manager.

2. Click on the desired Bot Manager configuration .
3. Click Delete Bot Manager Config.
4. Type DELETE.
5. Click Delete.