Skip to main content
Version: 1.5.1

Splunk Enterprise Security

SIEM Platform Observability

Send processed telemetry data to Splunk Enterprise Security SIEM platform.

Synopsis

The Splunk Enterprise Security target sends security telemetry to Splunk ES using the HTTP Event Collector (HEC) with security-optimized index configuration and CIM normalization. This target extends standard Splunk HEC configuration with security-specific data models and correlation search integration.

Schema

targets:
- name: <string>
type: splunk
properties:
endpoints:
- endpoint: <string>
auth_type: <string>
token: <string>
secret: <string>
index: <string>
sourcetype: <string>
source: <string>
batch_size: <integer>
timeout: <integer>
tcp_routing: <boolean>
use_compression: <boolean>
insecure_skip_verify: <boolean>
field_format: <string>
debug:
status: <boolean>
dont_send_logs: <boolean>

Configuration

Base Target Fields

FieldTypeRequiredDescription
namestringYUnique identifier for this target
descriptionstringNHuman-readable description
typestringYMust be splunk
pipelinesarrayNPipeline names to apply before sending
statusbooleanNEnable (true) or disable (false) this target

Splunk ES Connection

FieldTypeRequiredDescription
endpointsarrayYArray of Splunk HEC endpoint configurations
endpoints[].endpointstringYSplunk HEC URL (e.g., https://splunk.example.com:8088/services/collector)
endpoints[].auth_typestringNAuthentication type (token, secret). Default: token
endpoints[].tokenstringY*HEC token for authentication
endpoints[].secretstringY*Bearer token from environment variable

* token required when auth_type is token, secret required when secret

Event Configuration

FieldTypeRequiredDescription
indexstringNDefault Splunk index (e.g., main, security, notable)
sourcetypestringNDefault sourcetype for events
sourcestringNDefault source for events

Batch Configuration

FieldTypeRequiredDescription
batch_sizeintegerNNumber of events to batch before sending. Default: 10000
timeoutintegerNConnection timeout in seconds. Default: 30

Connection Settings

FieldTypeRequiredDescription
tcp_routingbooleanNEnable TCP routing header. Default: false
use_compressionbooleanNEnable GZIP compression. Default: true
insecure_skip_verifybooleanNSkip TLS certificate verification. Default: false

Normalization

FieldTypeRequiredDescription
field_formatstringNApply CIM normalization. Recommended: ASIM or custom

Debug Options

FieldTypeRequiredDescription
debug.statusbooleanNEnable debug logging for this target
debug.dont_send_logsbooleanNLog events without sending to Splunk ES

Details

Security Index Configuration

Recommended Indexes:

  • main: Default index for general security events
  • security: Dedicated security events index
  • notable: Notable events generated by correlation searches
  • threat_activity: Threat intelligence indicators
  • audit: Audit trail and compliance events

Index Naming Conventions:

  • Use descriptive index names matching data categories
  • Separate indexes for different security zones
  • Configure index retention based on compliance requirements
Index Permissions

Ensure HEC token has write permissions for configured indexes. Configure index permissions in Splunk Settings � Data � HEC tokens.

CIM Normalization

Common Information Model (CIM):

  • Splunk's standard for field naming and categorization
  • Required for Enterprise Security correlation searches
  • Enables pre-built dashboards and reports
  • Provides consistent data model across sources

CIM Data Models:

  • Authentication: Login events, authentication failures
  • Network Traffic: Firewall logs, network sessions
  • Endpoint: Process execution, file modifications
  • Malware: Anti-virus detections, malware events
  • Intrusion Detection: IDS/IPS alerts
  • Change Analysis: Configuration changes, account modifications

Field Mapping:

  • src / dest: Source and destination systems
  • user / dest_user: User accounts
  • action: Event action (allowed, blocked, success, failure)
  • vendor_product: Vendor and product identification

Notable Events Integration

Notable Event Creation:

  • Correlation searches generate notable events
  • Notables stored in notable index
  • Events require CIM-compliant field mapping
  • Custom correlation searches reference specific sourcetypes

Event Classification:

  • Configure urgency field for event prioritization
  • Set security_domain for categorization
  • Include risk_object for entity risk scoring

Correlation Search Compatibility

Search Requirements:

  • Events must conform to CIM data models
  • Sourcetypes must map to CIM categories
  • Field extractions must match CIM field names
  • Time field (_time) required for all events

Custom Correlation Searches:

  • Reference specific sourcetypes in search queries
  • Use CIM-compliant field names in search logic
  • Configure search scheduling and trigger conditions

Performance Optimization

Batch Configuration:

  • Larger batches reduce HEC API calls
  • Balance batch size against indexing latency
  • Default batch_size: 10000 suitable for most workloads

Compression:

  • GZIP compression enabled by default
  • Reduces network bandwidth significantly
  • Minimal CPU overhead for compression

Load Balancing:

  • Configure multiple HEC endpoints for high availability
  • Events distributed randomly across endpoints
  • Automatic failover to available endpoints
HEC Token Limits

Splunk HEC has per-token throughput limits. For high-volume deployments, use multiple HEC tokens or increase token limits in Splunk configuration.

Security Best Practices

HEC Token Management:

  • Create dedicated HEC tokens for DataStream
  • Use separate tokens for different environments
  • Rotate tokens periodically
  • Disable unused tokens

TLS Configuration:

  • Always enable TLS for production deployments
  • Verify server certificates (insecure_skip_verify: false)
  • Use certificate pinning for enhanced security

Index Security:

  • Configure role-based access control for indexes
  • Separate indexes for different security zones
  • Enable audit logging for index access

Examples

Basic Security Events

Sending security events to Splunk Enterprise Security...

targets:
- name: splunk-security
type: splunk
properties:
endpoints:
- endpoint: https://splunk.example.com:8088/services/collector
token: "${SPLUNK_HEC_TOKEN}"
index: security
sourcetype: datastream:security

With CIM Normalization

Applying custom normalization for CIM compliance...

targets:
- name: splunk-es-normalized
type: splunk
properties:
endpoints:
- endpoint: https://splunk.example.com:8088/services/collector
token: "${SPLUNK_HEC_TOKEN}"
index: security
sourcetype: datastream:security:cim
field_format: ASIM

Notable Events

Sending events to notable index for correlation search integration...

targets:
- name: splunk-notables
type: splunk
properties:
endpoints:
- endpoint: https://splunk.example.com:8088/services/collector
token: "${SPLUNK_HEC_TOKEN}"
index: notable
sourcetype: datastream:notable
source: DataStream

High-Availability Configuration

Multiple Splunk HEC endpoints for high availability...

targets:
- name: splunk-es-ha
type: splunk
properties:
endpoints:
- endpoint: https://splunk-hec1.example.com:8088/services/collector
token: "${SPLUNK_HEC_TOKEN}"
- endpoint: https://splunk-hec2.example.com:8088/services/collector
token: "${SPLUNK_HEC_TOKEN}"
- endpoint: https://splunk-hec3.example.com:8088/services/collector
token: "${SPLUNK_HEC_TOKEN}"
index: security
batch_size: 10000
use_compression: true

Threat Intelligence

Forwarding threat intelligence indicators to Splunk ES...

targets:
- name: splunk-threat-intel
type: splunk
properties:
endpoints:
- endpoint: https://splunk.example.com:8088/services/collector
token: "${SPLUNK_HEC_TOKEN}"
index: threat_activity
sourcetype: datastream:threatintel
source: threat-feeds

Authentication Events

Sending authentication events with CIM-compliant sourcetype...

targets:
- name: splunk-authentication
type: splunk
properties:
endpoints:
- endpoint: https://splunk.example.com:8088/services/collector
token: "${SPLUNK_HEC_TOKEN}"
index: security
sourcetype: datastream:auth
batch_size: 5000

Production Configuration

Production-ready Splunk ES configuration with HA, compression, and security settings...

targets:
- name: splunk-es-production
type: splunk
properties:
endpoints:
- endpoint: https://splunk-hec1.example.com:8088/services/collector
token: "${SPLUNK_HEC_TOKEN}"
- endpoint: https://splunk-hec2.example.com:8088/services/collector
token: "${SPLUNK_HEC_TOKEN}"
index: security
sourcetype: datastream:security:production
source: datastream-director
batch_size: 10000
timeout: 30
use_compression: true
insecure_skip_verify: false
field_format: ASIM