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
        • Manage Sightline Precheck Settings
        • Customize Sightline Precheck Look and Feel
      • Custom Actions Overview
    • 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
  • Prerequisites
  • Enable Precheck
  • Customize Precheck implementation
  • Add exclusions
  • Manage exclusions
  • Export Precheck reports
Sightline Cyberfraud DefenseMitigation SettingsPrecheck Settings

Manage Sightline Precheck settings

Was this page helpful?
Previous

Customize Sightline Precheck look & feel

Next
Built with

Precheck is a Sightline validation that appears when HUMAN detects a new bot visiting your application for the first time. Because these bots have never visited your site, Sightline has no information about them. However, if the bot is malicious, you want to protect your site even on its first visit (such as protecting against scraping). Precheck tests these bots before they act. If the bot fails Precheck, then it can’t proceed to your site.

You can enable and customize how Precheck behaves and looks from Sightline settings.

Precheck is available with Custom ABR for web and HTML properties, but is incompatible with Custom ABR for API.

Prerequisites

  • Your Sensor version must be at least 9.2.7 or higher. See our installation instructions to learn how to update to the latest version.
  • Your application must be in production mode.

Enable Precheck

  1. Navigate to Sightline Cyberfraud Defense > Settings > Mitigation > Precheck Settings.
  2. Select the application you want to enable Precheck on from the Application name & Application ID dropdown menu.
  3. Select the Precheck Configuration tab.
  4. Turn on Precheck Enablement.
  5. Click the checkbox if you want to receive daily reports in your email. Otherwise, you can always return to this page to download the daily report manually.
  6. Click Save Changes.
  7. Click Save.

Precheck appears to first-time visitors on their first request on your application’s sensitive routes.

Customize Precheck implementation

Once you enable Precheck, you can manage how it works on your site.

Add exclusions

By default, Sightline embeds Precheck on pages that are most susceptible to scraping attempts. However, you can exclude Precheck on certain routes on your application using regular expressions (regex).

  1. Navigate to Sightline Cyberfraud Defense > Settings > Mitigation > Precheck Settings.
  2. Select the application you want to enable Precheck on from the Application name & Application ID dropdown menu.
  3. Select the Precheck Configuration tab.
  4. Click Add Exclusion.
  5. Enter the regex pattern for the path(s) you want to exclude.
  6. Click Validate Route. Precheck will confirm your regex matches at least one path in your application. Once it does, it will display these paths and the total number of matching paths.
  7. To confirm the paths that appear are correct, click Apply.
  8. To add more exclusions, repeat Steps 2-5.
  9. Click Save Changes.
  10. Click Save.

Manage exclusions

Once you’ve added one or more exclusions, they’ll appear in your Precheck Exclusion Settings. You can manage each exclusion with the following options:

  • Click the checkbox next to any exclusion to either enable or disable Precheck on matching routes.
  • Hover over and click remove to permanently delete the route.

Be sure to click Save changes to apply your updates.

Export Precheck reports

In addition to receiving Precheck reports daily to your email, you can also download reports from Precheck Settings.

Precheck reports are updated daily. Be sure to download a given day’s report before it’s replaced the next day.

If you download a report the same day you enable Precheck, then the report will have projected Precheck impact data. This is because Precheck hasn’t been active for a long enough time on your application. We recommend waiting a full day after enabling Precheck to download reports with actual impact data.

To download a report:

  1. Navigate to Sightline Cyberfraud Defense > Settings > Mitigation > Precheck Settings.
  2. Select the application you want to download the report from in the Application name & Application ID dropdown menu.
  3. Select the Precheck Configuration tab.
  4. Click the button to export your report.