Skip to main content

 

Splunk Lantern

Selecting the correct apps to integrate the Splunk platform and SOAR

 

SOAR is also not a replacement for the Splunk platform. However, it interacts with the Splunk platform in a number of ways that will improve your organizational security. This set of articles explains how it does that through the use of several integrations.

If you are a new Splunk SOAR customer, start with the guide Getting started with SOAR and then return to this article for some expert recommendations on how to best to use SOAR in conjunction with the Splunk platform to improve your processes.

Splunk SOAR is a security orchestration, automation, and response platform that combines security infrastructure orchestration, playbook automation, and case management capabilities. It integrates your team, processes, and tools to help you orchestrate security workflows, automate repetitive security tasks, and quickly respond to threats. A typical case workflow in SOAR involves the following steps:

  1. Preparation
  2. Investigation
  3. Containment
  4. Eradication
  5. Recovery
  6. Lessons Learned

The best use of Splunk SOAR is to only send events to it that need work done. You should not use it as a replacement for a SIEM, like Splunk Enterprise Security or for general notifications and alerts that don't require action.

SOAR is also not a replacement for a well designed SOC or experienced SOC analysts. Although SOAR is excellent at automating processes that are well-defined, it is more like a SOC intern than an experienced analyst. It can free up analysts' time for tasks that require more critical thinking. Additionally, the better your SOC processes are, the more useful SOAR will be to your team.

To understand how SOAR interacts with the Splunk platform, first review these key SOAR concepts:

  • Data sources. Inputs for SOAR.
  • Playbooks. A set of apps, actions, decisions, and logic to run certain tasks and create orchestration.
  • Actions. API calls to the services.
  • Apps. These interact with third-party services to run all kinds of actions. This is where the automation comes in.
  • Assets. A specific instance of the code in an app, otherwise thought of as a particular connection to a server. You will have one, along with a host name and credentials, for every Splunk instance you want to talk to.
  • Owners. Rule-based access control on who can interact with what connections.

clipboard_e074cb6ee4976832043ce87ba47ee8948.png

The Splunk platform can interact with any of the above functions. Read the descriptions below and then click into the expert guidance to learn how you can work with each one using Splunk apps.

The information below applies to SOAR and Splunk Enterprise Security (ES) integrations versions prior to ES 8.x. ES 8 introduced a streamlined and direct integration with SOAR. For more information on that integration, see Pair Splunk Enterprise Security with Splunk SOAR.

Next steps

Now that you understand the differences between these three apps and how they connect the Splunk platform and Splunk SOAR, check out the Splunk Lantern product tips for SOAR to learn how to do more.