For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
HUMAN DashboardHUMAN WebsiteRequest a Demo
Product GuidesEnforcer GuidesMobile SDKAPI ReferenceCustomer support
Product GuidesEnforcer GuidesMobile SDKAPI ReferenceCustomer support
  • Getting Started
    • Overview
    • Best practices
  • Sightline Cyberfraud Defense
    • About Sightline Cyberfraud Defense
    • Getting Started
    • What's different in Sightline Cyberfraud Defense
    • Sensor changelog
    • About the Overview Dashboard
    • Glossary
  • AgenticTrust
    • Getting started with AgenticTrust
    • AI Agents Monitoring Dashboard
    • AI Visitors Overview Dashboard
    • Manage AI Agent Permissions
    • Agentic Activity Priority
    • Agent Trust Levels
  • Account Defender
    • Account Defender Overview
    • Use Cases
    • Prerequisites
    • Getting Started with Account Defender
    • Optimizing Account Defender Detection
    • Validating Account Defender Integration
    • Risk Triggers
    • About Network Events
    • Troubleshooting
  • Bot Defender
    • Bot Defender Overview
    • Detection
      • Detection Overview
    • Bot Defender Policy Settings
    • Footprint
  • Credential Intelligence
    • Credential Intelligence Overview
    • How to Access the Breached Flag
    • Credential Intelligence FAQ
    • Credential Intelligence Dashboard
  • Code Defender
    • Code Defender Introduction
    • Getting Started with Code Defender
    • Code Defender Glossary
    • Website Risk Analyzer
  • Platform
    • Account settings
    • Manage users
    • Role permissions
    • Enforcer configurations
    • Page Type Mapping
  • Client-Side Integration
    • JavaScript tag
    • Improving first page performance
    • Use of cookies & web storage
    • Advanced client integration
LogoLogo
Login
Login
HUMAN DashboardHUMAN WebsiteRequest a Demo
On this page
  • Machine Learning and Predictive Models
  • Behavioral Patterns
  • Fingerprints
  • Detecting Good Bots
Bot Defender

Detection Overview

Was this page helpful?
Previous

Detection

Next
Built with

To identify automated traffic in real-time, the cloud-based HUMAN Detector processes hundreds of live signals collected on the client by the HUMAN Sensor. The detector calculates a risk score for every request which is embedded into a cookie that is later processed by the HUMAN Enforcer.

Machine Learning and Predictive Models

Bot Defender detection relies on Machine learning(ML) and predictive models continuously updated based on the analysis of vast amounts of data and signals. The Sensor collects hundreds of features, billions of anonymized data points, and historical data about bots and human behavior. The Detector uses this activity data to dynamically and accurately predict if a request is coming from a malicious bot, and correlates it with the known good and bad bots. The signals include tagging spoofed identifiers, surfacing malicious patterns automatically, spotting user-interaction anomalies within mouse clicks, screen touches, cadence and timing, and self-tuning to address the customer’s website structure and business metrics.

Behavioral Patterns

HUMAN invests significant resources in threat intelligence and advanced research. Its research team constantly investigates and explores evolving attack vectors, and new threat actors, tools and techniques. Using manual and automated tools, and internal and external resources, HUMAN researchers derive insights that are translated into new and improved detection algorithms. These algorithms provide the Detector with enriched behavioral patterns for bots of all sophistication levels and address diverse use cases and attacks across several verticals.

Fingerprints

In addition to the machine learning (ML)-based techniques and behavioral analysis, the Detector uses hundreds of indicators from the browser, mobile, and network collected by the Sensor. These indicators include HUMAN ID (cookie-based), device features such as visual and audio rendering capabilities, traffic source and type, window objects, attacker specific signatures, browser plugins, and extensions. The indicators are compared to a growing library of bad actor profiles built on anonymized and aggregated customer sets and multiple external resources.

Detecting Good Bots

Good bots are beneficial automated traffic sources, such as Google and Bing search engine crawlers and website monitoring services. In addition to the customer’s defined list of good bots, Bot Defender automatically flags good bots based on a constantly updated live feed derived from internal and external sources.