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
        • Mitigation Actions
        • Alerts and Notifications Actions
        • Data Export Actions
        • Other Actions
      • 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
  • Create an other action
  • Add an action to a Policy Rule
Sightline Cyberfraud DefenseMitigation SettingsCustom Action Settings

Other actions

Was this page helpful?
Previous

Custom Actions Overview

Next
Built with

Other actions let you manage events that match your policy rules without necessarily mitigating or sending an alert or data. You can learn how to create these actions with this article.

These actions only support acccount-related events.

Prerequisites

  • Appropriate role permissions to add and manage actions. By default, this is an Admin in Sightline.
  • An HTTP integration, which you can access from Platform Settings > Integrations > HTTP. For more information, see our help article.
  • If you want to send custom data, you need existing custom parameters first. See Set custom parameters for more information.

Create an other action

  1. Navigate to Sightline Cyberfraud Defense > Settings > Mitigation > Custom Action Settings.
  2. Under the Other section, click the type of action you want to create.
  3. Click + Add Action.
  4. Complete the following fields:
    • Action name: The name of the action and how it will appear in your HUMAN account.
    • Cooldown duration: The length of time that Sightline should wait to trigger this action each time it detects a match on the Policy Rule it’s assigned to.
    • Duration unit: The unit of time for the cooldown duration.
    • Integration: Select the integration you want to use.
    • Application data source: The application you want to send data from. You can only select one application per action.
    • Event type: The type of event you want to use this action for.
    • Content Settings: Select each field you want to include in the request. You can’t change any default fields.
  5. Click Save changes.

Your action has been created. Next, be sure to add it to a policy rule.

Add an action to a Policy Rule

Once you have an action, we recommend adding it to a policy rule.

Be sure your policy rule’s application and event type match the ones you chose above. Otherwise, the action won’t appear when you try to add it to the rule.

  1. Navigate to Sightline Cyberfraud Defense > Policies > Account Policies.
  2. Select a rule to edit or create a new rule. See our article for more on creating policy rules.
  3. From the Actions menu, click and drag the action to the THEN field.

  1. Finish any other changes to your policy rule, then click Simulate rule.
  2. Click Save changes.

Now, whenever Sightline detects an attack that matches the conditions in that policy rule, it will trigger your action automatically.