Skip to content
Integrations/Splunk HEC Compatible Receiver/Connection Guide
Connection Guide

Connect Splunk HEC Compatible Receiver Without Breaking the Audit Trail

Use this guide to connect Splunk HEC Compatible Receiver or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeLog collection
CategoryLogging
Checklist3 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect Splunk HEC Compatible Receiver and make sure the first collection lands cleanly.

  1. 1
    Generate or provision an HEC token in the platform connection settings.
  2. 2
    Configure your source system to POST events to the platform's HEC receiver endpoint using the Splunk authorization header.
  3. 3
    Validate the receiver returns a Splunk-compatible response (code=0).

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

hec_token

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

Access requirements depend on the collection mode and scope you choose.