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
      • Adobe Experience Platform
      • Auth0
      • AWS S3
      • Datadog
      • Email to Consumer
      • GCS
      • HTTP webhook
      • Okta
      • Slack
      • Splunk
      • Sumo Logic
      • Syslog
    • 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
  • Integrate with Splunk
PlatformIntegrations

Splunk integration

Was this page helpful?
Previous

Sumo Logic integration

Next
Built with
Data export Data export actions

The Splunk integration lets you forward data to your Splunk Cloud or enterprise instance for further analysis with Splunk’s HTTP Event Collector (HEC). This lets you leverage HUMAN data alongside your existing logs and metrics within your Splunk platform. You can use the Splunk integration to create a data export or trigger it with a data export action.

Prerequisites

  • Appropriate role permissions to create and manage integrations

Integrate with Splunk

  1. Navigate to Platform Settings > Integrations and click the Splunk integration.
  2. Click Add Integration.
  3. Provide the following:
    • Integration name: How the integration will appear in your HUMAN account.
    • Authentication method: Select the authentication method for sending data.
      • If you select Web application firewall (WAF), also provide allowed IPs.
    • URL: The Splunk URL to send data to. This should follow Splunk’s HEC URI standard form for Splunk Enterprise: <protocol>://<host>:<port>/<endpoint>. See Splunk’s Set up and use HTTP Event Collector in Splunk Web for more information.
    • Protocol: The HTTP protocol to use.
    • Provide an SSL certificate: If you select TLS, upload a CRT file of your SSL certificate.
    • Headers (optional): Add any header names and values as needed. If any duplicate header keys are provided, the webhook will only send the later one.
      • If you are adding the Authorization header, you must include the keyword Splunk before the HEC token.
  4. Click Test Connection.
  5. Once the test succeeds, click Save changes.

You have successfully configured a Splunk integration. Make sure to use the integration to create a data export or trigger it with a data export action.