---
sourceDocument: Zurich Security Management
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/security-management

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# Splunk Enterprise Security event ingestion integration

# Splunk Enterprise Security event ingestion integration {#ariaid-title1}

* Release version: Zurich
* 
* Updated July 31, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Splunk Enterprise Security Event Ingestion Integration

The Splunk Enterprise Security (ES) notable event ingestion integration with the Security Incident Response (SIR) product enables security incident analysts to collect and process notable events (notables) efficiently.
This integration allows for continuous data ingestion based on a configured polling schedule, aiding analysts in identifying and responding to potential cyber threats.
Notable events can be automatically correlated and ingested into the ServiceNow AI Platform, providing SOC analysts with visibility into event data for investigation and remediation.
Show full answer Show less  

## Key Features

* Create multiple notable event ingestion profiles for specific threats (e.g., phishing, malware).
* Forward notable events on-demand from the Splunk ES incident review console to create SIR security incidents.
* Utilize drag-and-drop mapping of Splunk event fields to SIR incident fields.
* Preview SIR incident layouts to validate event mapping.
* Ingest both historical and current notable events at configurable intervals.
* Filter out low-priority events that do not meet SIR criteria.
* Aggregate events to avoid duplicate security incidents based on matching values.
* Update notable events based on SIR incident conditions via a bi-directional interface.

## Key Outcomes

By implementing this integration, ServiceNow customers can enhance their security operations by automating the ingestion of notable events, streamlining incident response, and ensuring that security data is consistently updated across platforms. The required ServiceNow plugins and applications must be installed in a specified order to facilitate a smooth integration process.

Note: A MID Server is necessary for on-premise Splunk deployments, while it is not required for Splunk Cloud services.  
The Splunk Enterprise Security notable event ingestion integration with the Security Incident Response (SIR) product allows security
incident analysts to collect and process notable event data (referred to as
notables).

## Overview of Splunk Enterprise Security event ingestion integration {#splunk-event-ingest-overview-security__section_aqv_bhj_jfb}

Data is ingested continually based on a configured polling schedule and it is used by
analysts to identify and respond to potential cyber threats. Security events that are
collected can be correlated into notable events in Splunk Enterprise Security and
then ingested automatically with this integration. Also, individual notable events can be
manually forwarded on-demand from the Splunk Enterprise Security Incident Review
console and reporting interface into the Security Incident Response product of the
ServiceNow AI Platform to create security incidents.

This integration provides a security operations center (SOC) analyst with visibility to
notable events and related contributing event data. This data can be integrated into ServiceNow AI Platform
Security Incident Response (SIR) security
incidents for further investigation and remediation. Profiles are created in your ServiceNow AI Platform instance to handle different notable event types that are created
via correlation searches in Splunk Enterprise Security. These profiles customize how
different Splunk event fields are displayed on SIR security incidents.

## Key features {#splunk-event-ingest-overview-security__section_irs_fhj_jfb}

This integration includes the following key features:

* Create multiple notable event ingestion profiles to create SIR security incidents for specific types of threats such as phishing and malware and unauthorized access attempts.
* Create multiple event profiles for on-demand event forwarding from your Splunk ES incident review console to create SIR security incidents.
* Drag-and-drop mapping of Splunk notable event field values to associated SIR security incident fields.
* A preview of the SIR security incident layout based on sample notable events to validate event mapping details.
* Ingest historical notable events as well as ongoing, new, and updated notable events on configurable intervals.
* Filter out notable events that do not meet SIR incident generation criteria, for example, low priority events, events that have yet to achieve a specific status, and so on.
* Aggregate events or alerts to existing SIR security incidents based on matching field values to avoid duplicate security incidents.
* Update notable events based on SIR incident creation and/or closure conditionals via a bi-directional interface to keep Splunk ES notable event updates in sync with the ServiceNow SIR incident status.
{#splunk-event-ingest-overview-security__ul_jzw_t3j_jfb}

## Supported ServiceNow AI Platform versions {#splunk-event-ingest-overview-security__section_x15_vjm_y2b}

The com.snc.si_dep plugin is required for this integration. This plugin automatically
installs all the dependencies that are required to support the Security Incident Response product. Install and activate this plugin before
installing and activating the other Security Operations applications.  
The following Security Operations applications must be installed and activated from the ServiceNow Store. Install and then activate one application at a time in the order listed below to ensure a smooth installation:

1. Security Integration Framework
2. Security Support Common
3. Security Incident Response
{#splunk-event-ingest-overview-security__ol_xcx_jzk_tgb}

For more information about installing the Security Operations core applications, see
[Get entitlement for a Security Operations product or application](https://www.servicenow.com/docs/~2u0~c5D1BrLZsmjUfocXQ "The first step in installing a Security Operations application is to verify that the application or the product and its associated applications have valid ServiceNow entitlements.") and [Activate a ServiceNow Store application](https://www.servicenow.com/docs/cbsCnF1HDp9yU6mvFeqGtg "After an application has been given entitlement, you must activate its dependencies plugin and activate the application. This process also applies to applications downloaded to sub-production instances.").

## ServiceNow Addons {#splunk-event-ingest-overview-security__section_sw3_mqb_2gb}

The ServiceNow Security Operations Event Ingestion Addon for Splunk ES is required only if you prefer to forward events manually
from your Splunk Enterprise Security Incident Review console into your ServiceNow AI Platform instance. This ServiceNow addon is
available in [splunkbase](https://splunkbase.splunk.com/).

This ServiceNow Security Operations Event Ingestion Addon for Splunk Enterprise application in splunkbase is not required for the
automated alert ingestion that is supported by the integration.

## Splunk Supported versions {#splunk-event-ingest-overview-security__section_j25_1jm_y2b}

This integration has been tested with:

* Splunk Enterprise version 10.0.0 and earlier.
* Splunk Enterprise Security application version 8.3.0 and earlier.
{#splunk-event-ingest-overview-security__ul_ozj_5yk_nhc}

## MID Server {#splunk-event-ingest-overview-security__section_e2y_5rb_2gb}

This integration requires an installed and configured MID Server in your ServiceNow AI Platform® instance to connect to the Splunk
service when the Splunk server is deployed within your corporate network.
If you are using the Splunk Cloud service, a MID Server is not required.
See [MID Server](https://www.servicenow.com/docs/access?context=mid-server-landing&version=zurich&pubname=zurich-servicenow-platform&ft:locale=en-US) for more information about MID Servers.

## References {#splunk-event-ingest-overview-security__section_y2r_wqb_2gb}

{#splunk-event-ingest-overview-security__table_axk_n23_2gb__entry__3}

| Reference | Document Identifier | Document Title |
|-|-|-|
| 1 | Splunk product website | [Splunk Enterprise Security product website](https://www.splunk.com/en_us/software/enterprise-security.html). |
[ ]

{#splunk-event-ingest-overview-security__table_axk_n23_2gb}

## Checklist {#splunk-event-ingest-overview-security__section_gpy_lhf_dhb}

For a printable checklist of these topics, see [Checklist for Splunk Enterprise Security Notable Event Ingestion integration](https://www.servicenow.com/docs/4pG56QxWajeYYjrsgH_~9w "Use this checklist to guide you through all the tasks of the integration. The following checklist includes setup and installation tasks and examples of use cases that include expected results for the integration."). You can use
this list to monitor your progress as you work through the tasks of the integration.