Configure search in Splunk SOAR (On-premises)
In earlier releases of Splunk SOAR (On-premises) search was handled by an embedded version of Splunk Enterprise. Beginning with release 6.2.0, Splunk SOAR (On-premises) uses PostgreSQL full-text search, which has been modified to accept the *
wildcard. For search syntax and examples, see Search within Splunk SOAR (On-premises).
To improve the ability to get Splunk SOAR (On-premises) data into a Splunk Cloud Platform or Splunk Enterprise deployment, support was added for Universal Forwarders. For information about configuring forwarders, see Configure forwarders to send SOAR data to your Splunk deployment.
Splunk SOAR (On-premises) also supports using an Elasticsearch instance for indexing SOAR data.
This list summarizes the available options for configuring forwarding data to a Splunk Enterprise or Splunk Cloud Platform instance from Splunk SOAR (On-premises).
- Splunk Cloud Platform - by configuring a Universal Forwarder Credentials Package and Universal Forwarders
- Splunk Enterprise - by configuring Universal forwarders
- Elasticsearch - by configuring a forwarder
Configure Splunk SOAR (On-premises) to forward data to Splunk Cloud Platform
Integrating with Splunk Cloud Platform requires the following actions:
- Configure Universal Forwarders and a Universal Forwarder Credentials Package. See Configure forwarders to send SOAR data to your Splunk deployment.
Configure Splunk SOAR (On-premises) to forward data to Splunk Enterprise
Integrating with Splunk Enterprise requires the following actions:
- Configure Universal Forwarders. See Configure forwarders to send SOAR data to your Splunk deployment.
Configure the scope of global search using the REST API
You can control the scope used by global search in Splunk SOAR (On-premises), using the /rest/feature_flag/restrict_global_search
REST API endpoint. See /rest/feature_flag/<feature_flag_name> for details of the /rest/feature_flag REST API, the parameters it accepts, and examples for changing settings using the endpoint.
In the interest of performance, restrict_global_search defaults to "on" and has the following settings applied:
- Searching the database tables app_run, action_run, and playbook_run are turned off.
- The maximum age of database table entries will be searched is 30 days.