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
On this page
  • Sensitive Paths
  • Past Fraud Cases
Account Defender

Optimizing Account Defender Detection

Was this page helpful?
Previous

Validating Account Defender Integration

Next
Built with

Sensitive Paths

HUMAN Account Defender makes use of sensitive paths. A sensitive path is a path that:

  • Your organization wants to protect from fraudulent activities or abuse by competitors (for example, checking a shopping cart, withdrawing funds, executing a transaction, sending an internal message, etc.)
  • Can be used to cause damage to other assets or abused by attackers (for example, disabling notifications, changing email address, changing shipping address, disabling MFA, etc)

During the onboarding, the HUMAN team maps out your web-site for sensitive paths using observation and threat intelligence. If you know of any such paths, please give us these details:

  • Path URL/regex (for example, users/.*/edit_billing)
  • Name to be displayed in Account Defender screens and reports

Past Fraud Cases

If your organization has been a target to fraud attempts in the past, we encourage you to provide us with information about such cases, including:

  • Web logs
  • IP addresses
  • Account IDs
  • Attack patterns

This will help us fine-tune Account Defender to better address your organization’s needs.