Bot management
Cloudflare has bot management capabilities to help identify and mitigate automated traffic to protect domains from bad bots. Bot Fight Mode and Super Bot Fight Mode are options available on Free and Pro/Business accounts respectively. They offer a subset of features and capabilities available for Enterprise accounts. This reference architecture diagram focuses on Enterprise Bot Management available for Enterprise customers.
With Enterprise Bot Management ↗ customers have the maximum protection, features, and capability. A bot score ↗ is exposed for every request. Cloudflare applies a layered detection approach to Bot Management with several detection engines that cumulatively can impact the bot score. A bot score is a score from 1 to 99 that indicates the likelihood that the request came from a bot. Scores below 30 are commonly associated with bot traffic and customers can then take action on this score with WAF custom rules ↗ or Workers ↗. Additionally, customers can view this score along with other bot specifics like bot score source, bot detection IDs, and bot detection tags in the Bots, Security Analytics, and Events dashboards; these fields can also be seen in more detailed logs in Log Explorer or, with Log Push, logs with these respective fields can be exported to 3rd party SIEMs/Analytics platforms.
- Bot Score: A bot score is a score from 1 to 99 that indicates how likely that request came from a bot. A score of 1 means Cloudflare is certain the request was automated.
- Bot Score Source: Bot Score Source is the detection engine used for the bot score.
- Bot Detection ID: Detection IDs are static rules used to detect predictable bot behavior with no overlap with human traffic. Detection IDs cause a bot to receive a score source of heuristics with a score of 1.
- Bot Tag: Bot tags provide more detail about why Cloudflare assigned a bot score to a request.
- Verified Bots: Cloudflare maintains a list of “Verified” good bots ↗ which can be used in policies to insure good bots such as those associated with a search engine are not blocked.
- AI Bots: If the feature is enabled, Cloudflare will detect and block verified AI bots that respect
robots.txtand crawl rate, and do not hide their behavior from your website. The rule has also been expanded to include more signatures of AI bots that do not follow the rules.
- Heuristics: Cloudflare conducts a number of heuristic checks to identify automated traffic, and requests are matched against a growing database of malicious fingerprints. The Heuristics engine immediately gives automated requests a score of 1.
- Machine Learning (ML): The ML engine accounts for the majority of all detections, human and bot. The ML model leverages Cloudflare’s global network, which proxies billions of requests daily, to identify both automated and human traffic. The ML engine produces scores 2 through 99.
- Anomaly Detection (AD): The AD engine is an optional detection engine that uses a form of unsupervised learning. Cloudflare records a baseline of a domain’s traffic and uses the baseline to intelligently detect outlier requests. Anomaly Detection is user agent-agnostic and can be turned on or off by your account team. Cloudflare does not recommend AD for domains that use Cloudflare for SaaS or expect large amounts of API traffic. The AD engine immediately gives automated requests a score of 1.
- JavaScript Detections (JSD): The JSD engine identifies headless browsers and other malicious fingerprints. This engine performs a lightweight, invisible JavaScript injection on the client side of any request. The JSD engine either blocks, challenges, or passes requests to other engines. JSD is enabled by default but is completely optional.
Cloudflare bot score and bot traffic analysis is available in several locations.
-
Bots dashboard: Customers can easily see bot activity up to 30 days back and filter on bot score and other bot, traffic, and request filters. The bot feedback loop allows customers to report back to Cloudflare any false positives or false negatives for further investigation.
-
Security Analytics: Security Analytics brings together all of Cloudflare’s detection capabilities in one dashboard and provides a broad view of all traffic across the site. The Bots Likelihood graph and widget provide visibility and allow customers to easily view and filter based on bot score and respective categorization of Automated, Likely Automated, Human, and Likely Human.
-
Events: Events displays all events the WAF took action on. Events and logs can easily be filtered by bot score and other bot, traffic, or request criteria.
-
Log Explorer: Customers can use Log Explorer to pull additional detailed log data. Logs can easily be filtered by bot score and other bot, traffic, or request criteria.
-
Log Push: Customers can also export logs to a third party SIEM or Analytics platform. Bot score, bot score source, bot detection IDs, and bot detection tags can all be exported as part of the logs.
- Client request is sent to the closest Cloudflare Data Center via anycast ensuring low latency.
- Cloudflare applies a layered approach for bot detection; each detection mechanism impacts the bot score assigned by Cloudflare to every request. Every request is assigned a bot score between 1-99 inclusive.
- Once the client request has been processed by all of Cloudflare’s detection engines and assigned a bot score, defined security policies will be executed, some of which may also be leveraging bot score. Various actions can be taken based on the assigned bot score including the block, allow, rate limit, NoCAPTCHA Challenge.
- Cloudflare provides analytics and insights into traffic and requests traversing the Cloudflare network. Customers can use the Bots, Security Analytics, Events, and Log Explorer dashboards to understand the overall traffic and bots activity across their site. Customers can also export logs to third party SIEM and Analytics Platforms.