Splunk Stream is the purpose-built wire data collection and analytics solution from Splunk. Passively capture packets, dynamically detect application, parse the protocol, and send metadata back to your Indexer for over 30 protocols. Detection only for over 300 commercial protocols, even if encrypted.
Targeted full packet capture to NAS for forensic investigation of raw packets. Aggregate data using familiar SPL aggregation methods to reduce the volume of data indexed. Capture Flow-type records, including NetFlow v5, v9, jFlow, and sFlow, and IPFIX, and send Flow Records directly into your Indexers, with optional filtering and aggregation.
Ingest PCAP files in real-time or on-demand. Create MD5 hashes of file attachments for Threat Intelligence correlations using Splunk ES, and extract and store those reassembled files for forensic or DLP purposes. Parse SQL statements to help understand user intent. Understand IP client-server connections with patent-pending visualization.
For detailed installation instructions, see Install Splunk Stream.
Splunk Stream includes the following components:
• splunk_app_stream: splunk_app_stream provides configuration management for Splunk_TA_stream. You can use splunk_app_stream to configure event capture for multiple network protocols. See Supported Protocols.
• Splunk_TA_stream: Splunk_TA_stream contains the Stream Forwarder (streamfwd binary), which passively captures event data from network devices, and sends that data to Splunk Enterprise indexers using a “Wire Data” modular input.
• Independent Stream forwarder: Splunk Stream supports independent Stream forwarder installation on compatible Linux machines. Independent Stream Forwarder deployment is useful, for example, for capturing network data from Linux hosts that you want to monitor as part of a network service in a Splunk IT Service Intelligence (ITSI) deployment. No Splunk platform components are required on the machine where you install Stream Forwarder.
Important: You must be running splunkd with “root” privileges for the streamfwd binary to capture data. To set privileges on *nix:
On Windows, you must be running as administrator or install winpcap separately.
All captured events have “source=stream:stream-id” and “sourcetype=stream:protocol”, where ID is typically the name of a protocol. For example, “sourcetype=stream:http.”
Splunk Stream version 7.1.1 requires Splunk Enterprise version 6.4.0 or later.
For complete Splunk Stream documentation, see Splunk Stream documentation.