Splunk® App for SOAR Export

Use the Splunk App for SOAR Export to Forward Events

Acrobat logo Download manual as PDF


This documentation does not apply to the most recent version of Splunk® App for SOAR Export. For documentation on the most recent version, go to the latest release.
Acrobat logo Download topic as PDF

About the Splunk App for SOAR Export

Splunk SOAR can use the Splunk platform as a source of data by ingesting events. The Splunk App for SOAR Export, formerly known as Phantom App for Splunk, is required to configure Splunk Enterprise or Splunk Cloud Platform as a data source for getting data into Splunk SOAR.

What does the Splunk App for SOAR Export do?

The following image shows an example of how a standalone Splunk SOAR instance is integrated with a Splunk platform environment.

This diagram shows how the Splunk App for SOAR Export translates CIM data from the Splunk platform to CEF data for Splunk SOAR. Splunk Cloud Platform and Splunk Enterprise are shown on the left. Arrows from both Splunk Cloud Platform and Splunk Enterprise point to a box labeled Splunk Alerts, which contains Saved Search, Data Model, and Splunk ES Notable. The Splunk App for SOAR Export perform mapping to CEF fields for Saved Search and Data Model, and CIM to CEF translation for Splunk ES Notables. Finally, CEF events are sent from the Splunk platform to Splunk SOAR.

The Splunk App for SOAR Export is installed as an app on the Splunk platform and forwards events to Splunk SOAR. The Splunk platform environment consists of raw events or Common Information Model (CIM) data, while Splunk SOAR uses the Common Event Format (CEF). The Splunk App for SOAR Export acts as a translation service between the Splunk platform and Splunk SOAR by performing the following tasks:

  • Mapping fields from Splunk platform alerts, such as saved searches and data models, to CEF fields.
  • Translating CIM fields from Splunk Enterprise Security (ES) notable events to CEF fields.
  • Forwarding events in CEF format to Splunk SOAR, which are stored as artifacts.

How Splunk SOAR integrates with the Splunk platform

The following image shows how Splunk SOAR is integrated into a Splunk environment.

From left to right, a REST data icon is connected to App APIs, which is connected to the Internet and Firewall using TCP ports 80 and 443, which is then connected to a standalone Splunk SOAR instance. Also connected to the Splunk SOAR instance as REST data over TCP port 443 or custom ports, and analysts and admins over TCP ports 22 and 443. The Splunk SOAR instance is connected to an external Splunk instance with the Splunk App for SOAR Export installed. Specifically, the Splunk SOAR instance connects to the forwarders on the external Splunk instance over TCP ports 9996 and 9997, and to the search head over TCP ports 8089 and 443.

Before you install the Splunk App for SOAR Export, make sure you review the requirements.

Last modified on 29 June, 2023
  NEXT
Splunk App for SOAR Export release notes

This documentation applies to the following versions of Splunk® App for SOAR Export: 4.1.135

Was this documentation topic helpful?


You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters