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
    • 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
Account Defender

Prerequisites

In order to provide the most value, Account Defender requires direct access and visibility to traffic for both of our initial account takeover and account creation use cases.

Our machine learning models will learn individual user profiles based upon their typical actions. In order to monitor these accounts and determine fraudulent activities, Account Defender needs context to all relevant actions performed by users in a post-login environment. By providing full visibility to activities conducted post login, we can build an accurate profile of user behavior that will allow HUMAN to determine if specific actions are fraudulent.

Since all environments are different, we offer a multitude of methods by which to define these parameters. Refer to Basic Account Defender Integration to see, which method suits your environment best.

In cases where the fraudulent action happens via a third party (e.g., HyperWallet), we will require some minor additional steps to provide the audit of those actions to HUMAN (e.g. when receiving a call on a web hook, report that to HUMAN via our APIs).

Once HUMAN has access to all relevant traffic in our backend engine, our detection algorithms will go to work.

Was this page helpful?
Previous

Getting started with Account Defender

Next
Built with