Splunk® SOAR (On-premises)

Install and Upgrade Splunk SOAR (On-premises)

The classic playbook editor will be deprecated in early 2025. Convert your classic playbooks to modern mode.
After the future removal of the classic playbook editor, your existing classic playbooks will continue to run, However, you will no longer be able to visualize or modify existing classic playbooks.
For details, see:
This documentation does not apply to the most recent version of Splunk® SOAR (On-premises). For documentation on the most recent version, go to the latest release.

System requirements for production use

Systems for production must meet or exceed the listed requirements:

System Area Requirement
Hypervisor for virtual machine images. VMware vSphere ESX/ESXi 5 or later
Processor 1 server-class CPU, 4 to 8 cores
Memory Minimum of 16GB RAM, 32GB recommended
Storage needs storage for multiple volumes:
  • Phantom data: 500GB
    • mounted as either /opt/phantom/data or <$PHANTOM_HOME>/data
      The PostgreSQL database will be stored underneath the Phantom Data mount at: <$PHANTOM_HOME>/data/db
  • Embedded Splunk Enterprise: 500GB
    • mounted as /opt/phantom/data/splunk or <PHANTOM_HOME>/data/splunk
  • File share volumes: 500GB
    • mounted as /opt/phantom/vault or <PHANTOM_HOME>/vault

Disk space requirements vary based on the volume of data consumed and the size of your production environment.

Network A one-gigabit network interface
System utilities
  • cron
    • On privileged deployments, the phantom user must have permission to create cron jobs.
    • On unprivileged deployments, the user account that runs must have permission to create cron jobs.
  • ntp

If you use the Files feature to store virtual machine snapshots or other large-format data, it is recommended to have a larger volume for storage.

Last modified on 12 April, 2024
System requirements for evaluation use   ports and endpoints

This documentation applies to the following versions of Splunk® SOAR (On-premises): 5.1.0


Was this topic useful?







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