Set up your ServiceNow AI Platform instance for the Splunk Enterprise Security integration
Summarize
Summary of Set up your ServiceNow AI Platform instance for the Splunk Enterprise Security integration
This guide outlines the necessary setup tasks for integrating your ServiceNow AI Platform instance with Splunk Enterprise Security. Completing these tasks ensures a smooth installation and configuration of the application from the ServiceNow Store.
Show less
Key Features
- Required Roles: Ensure the following roles are assigned:
- snsi.ingestionprofileadmin
- snsi.admin (inherits required permissions)
- snsecsplunkes.apiaccountaccess (for manual event forwarding)
- snsi.analyst (for working with security incidents)
- Version Compatibility: Use Splunk API version 7.2.6 or later.
- MID Server Setup: Required if Splunk is on a corporate network; not needed for the cloud version.
- Required Plugins: Activate the Security Incident Response Dependency plugin (com.snc.sidep) and other essential Security Operations applications in a specified order.
Key Outcomes
By completing the setup tasks, you will have a properly configured ServiceNow AI Platform instance ready for the integration. The next step involves installing the Splunk Enterprise Security Notable Event Ingestion application from the ServiceNow Store, which will facilitate the integration process.
The following section lists the setup tasks that you are required to complete in your ServiceNow AI Platform® instance prior to installing the application from the ServiceNow Store.
Role required: sn_si.ingestion_profile_admin.
Refer to the following table and verify that you have completed all the listed tasks before you download and install the application to ensure a smooth installation and configuration.
- Verify that you have assigned the required ServiceNow AI Platform® and
Security Incident Response (SIR)
roles.
The following roles are required for the installation, setup, and use of the integration in your ServiceNow AI Platform® instance.
- A user with the ServiceNow AI Platform® administrator role (admin) installs the application from the ServiceNow Store and assigns the security incident administrator (sn_si.admin) role.
- If you want to forward notable events manually from Splunk Enterprise Security for this integration, a user with the ServiceNow AI Platform® admin role assigns a user with the
(sn_sec_splunkes.api_account_access) role in the ServiceNow AI Platform®. This role permits a user with the Splunk Enterprise Security administrator role to access the API in the
ServiceNow AI Platform® that is required for manual event
forwarding for this integration.
The (sn_sec_splunkes.api_account_access) role is not required for the integration if you are ingesting notable events automatically from Splunk Enterprise Security into your ServiceNow AI Platform® instance.
- A user with the sn_si.ingestion_profile_admin role oversees the following tasks in the ServiceNow AI Platform®:
- Names, creates, and edits event profiles.
- Selects and maps values from Splunk Enterprise Security to ServiceNow AI Platform® security incidents.
- Previews security incident details for accuracy prior to finalizing the configuration.
- Schedules on-going notable event ingestion.
- Enables notable event updates when a SIR incident is created and closed.
- Assigns the security incident analyst (sn_si.analyst) role.
- Users with the sn_si.analyst work with security incidents.
For more information, see Managing roles.
- Assign the Splunk user role.
Assign a Security Analyst (ess_analyst) user role in Splunk ES to perform all integration-related activities on the Splunk server.
- Verify that you are using version 7.2.6 or later of the Splunk
API. Earlier versions are not supported.
If you have access to the Splunk Enterprise Security console, you have access to the API that is required for this integration. There is no other special setup required for the API.
- Verify that you have installed and configured a MID Server.
A MID Server in your ServiceNow AI Platform® instance is required to connect to the Splunk service if the Splunk server is deployed within your corporate network. For information, see MID Server.
If you are using the Splunk Enterprise Security Cloud service, a MID Server is not required.
- Verify that the ServiceNow core applications that are
required to support the integration are installed and activated.
The Security Incident Response Dependency plugin (com.snc.si_dep) is required. This plugin automatically installs all the dependencies that are required to support the Security Incident Response product. Install and activate this plugin before you install and activate the other Security Operations applications required by the integration.
Verify that the following Security Operations applications are installed and activated from the ServiceNow Store. If not installed, install and activate one application at a time in the following order to ensure a smooth installation.
- Security Incident Response
- Security Integration Framework
- Security Support Common
For more information about installing the Security Operations core applications, see Get entitlement for a Security Operations product or application and Activate a ServiceNow Store application.