WAAS bot protection provides visibility into bots and other automation frameworks accessing protected web applications and APIs.
Bots are categorized into the following Categories:
- Search Engine Crawlers- Bots systematically crawling and indexing the world wide web to index pages for online searching. Also known as spider bots or web crawlers.
- Business Analytics Bots- Bots that crawl, extract and index business related information.
- Educational Bots- Bots that crawl, extract and index information for educational purposes, such as academic search engines.
- News Bots- Bots that crawl, extract and index the latest news articles, usually for news aggregation services.
- Financial Bots- Bots that crawl, extract and index financial related data.
- Content Feed Clients- Automated tools, services or end-user clients that fetch web contents for feed readers.
- Archiving Bots- Bots that crawl, extract and archive web site information.
- Career Search Bots- Automated tools or online services that extract and index job related postings.
- Media Search Bots- Bots that crawl, extract and index media contents for search engine purposes.
This category contains various bots and other automation frameworks which cannot be classified by their activity or origin
- Generic Bots- Clients with attributes that indicate an automated bot.
- Web Automation Tools- Scriptable headless web browsers and similar web automation tools.
- Web Scrapers- Automated tools or services that scrape web site contents.
- API Libraries- Software code libraries for Web API communications.
- HTTP Libraries- Software code libraries for HTTP transactions.
- Request Anomalies- HTTP requests with anomalies that are not expected from common web browsers.
- Bot Impersonators- Bots and automation tools impersonating as known good bots to evade rate limitation and other restrictions.
- Browser Impersonators- Automated tools or services that impersonate common web browser software.
Users can create custom signatures to be used based on HTTP headers and source IPs. User-defined signatures are useful for tracking customer specific bots, self-developed automation clients and traffic that appears suspicious.
WAAS uses static and active methods for detecting bots.
Static detection examines each incoming HTTP request and analyzes it to determine whether it was sent by a bot.
Prisma Session Cookies set by WAAS are encrypted and signed to prevent cookie tampering. In addition, cookies include advanced protections against cookie replay attacks where cookies are harvested and re-used in other clients.
Deploying Bot Protection
- Create bot signature by using a combination of the following fields:
- HTTP Header name- specify HTTP header name to include in the signature
- Header Values- comma separated list of values to be matched on in the HTTP header. Wildcard is allowed.
Enabling active detections
- Choose actions to apply.
- Session Validation- action to apply when WAAS is unable to validate the session, either due to cookie tampering or cookie replay.
reCAPTCHA v2 integration
WAAS Users can enable Google’s reCAPTCHA v2 integration by specifying the site key, secret key and challenge type. According to the user’s preference and settings, WAAS will serve a reCAPTCHA challenge at the beginning of each new session, or when a request is suspected of being sent by an unknown bot.
reCAPTCHA v3 is NOT supported (v2 only).
- Enter theSite keyprovided during the site registration
- Enter theSecret keyprovided during the site registration
- Select theChallenge typespecified during the site registrationChallenge type MUST match the challenge type selected on the reCAPTCHA site registration form (invisible or checkbox) in order for the reCAPTCHA integration to function properly.WAAS reCAPTCHA v2 integration does NOT support "reCAPTCHA Android" type
- Choose a preferredfriction.reCAPTCHA will ONLY be served for GET HTTP requests. WAAS will block requests sent using other methods until a reCAPTCHA challenge is solved and the success result is encoded into the Prisma Session Cookie.
- By policy (reCAPTCHA as an action)- when selected, a new effect will be available in the Unknown bot categoryWhen the reCAPTCHA is selected, WAAS will serve an interstitial page with a reCAPTCHA challenge whenever the protection is triggered.If the end-user successfully passes the challenge, it will be recorded in the Prisma Session Cookie for the duration of the Success Expiration setting (default is 24 hours).
- Each new session- Every new session will start with an interstitial page containing the reCAPTCHA challenge. If the end-user successfully passes the challenge, it will be recorded in the Prisma Session Cookie for the duration of the Success Expiration setting (default is 24 hours).
- Set theSuccess Expiration(in hours).This field determines how long a successful solution to a reCAPTCHA challenge will remain valid. Once the expiration date has passed, a new reCAPTCHA challenge will be presented (based on the selected friction settings).
Bot protection events
- Known bots- if a known bot is detected, the event message and attack type will provide details regarding the bot classification.
- Unknown bots- if an unknown bot is detected, the event message and attack type would provide details regarding the bot classification
- User-defined bots- a used-defined bot has been detected.
- Session Validation- The web client failed to pass the bot-detection session validation checks (e.g. prisma session cookie has been tampered with etc.).
- Missing Cookie- client made a non GET request without a cookie.
- Failed reCAPTCHA verification: <error returned from Google verification API>- Google’s reCAPTCHA verification API has responded with an error message.
- <HTTP method> request when a reCAPTCHA page is required- As mentioned in the reCAPTCHA v2 integration section, reCAPTCHA will ONLY be served for GET HTTP requests. WAAS will block requests sent using other methods until a reCAPTCHA challenge is solved and an event carrying this message will be registered.
Bot Protection Actions
Requests that trigger a WAAS bot protection are subject to one of the following actions:
- Alert- The request is passed to the protected application and an audit is generated for visibility.
- Prevent- The request is denied from reaching the protected application, an audit is generated and WAAS responds with an HTML page indicating the request was blocked.
- Ban- Can be applied on either IP or Prisma Session IDs. All requests originating from the same IP/Prisma Session to the protected application are denied for the configured time period (default is 5 minutes) following the last detected attack.
- Allow (available for user-defined bots)- request is forwarded to the protected application and no audit is generated.
- reCAPTCHA- a page will be served with a reCAPTCHA v2 challenge to be solved before proceeding to the website.
A message at the top of the page indicates the entity by which the ban will be applied (IP or Prisma Session ID).
WAAS implements state, which is required for banning user sessions by IP address or Prisma Sessions. Because Defenders do not share state, any application that is replicated across multiple nodes must enable IP stickiness on the load balancer.