--- sourceDocument: Brazil Security Management sourceDocumentLink: https://www.servicenow.com/docs/r/security-management Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil 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: Brazil Updated September 10, 2026 ![](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 notable event ingestion integration with ServiceNow Security Incident Response (SIR) enables security analysts to continuously collect and process notable security events (notables) from Splunk Enterprise Security. These notables, which represent correlated security incidents like phishing or malware attempts, are ingested automatically or forwarded manually into ServiceNow SIR to create actionable security incidents. This integration provides SOC analysts with comprehensive visibility into notable events and their contributing data, facilitating efficient investigation and remediation within the ServiceNow AI Platform. Show full answer Show less ## Key Features * Creation of multiple ingestion profiles tailored to specific threat types (e.g., phishing, malware) for automatic SIR security incident creation. * Support for on-demand manual forwarding of notable events from the Splunk Enterprise Security Incident Review console to ServiceNow SIR. * Drag-and-drop mapping interface to align Splunk notable event fields with ServiceNow SIR incident fields, including layout previews for validation. * Ingestion of both historical and real-time notable events on configurable intervals. * Filtering capabilities to exclude low-priority or irrelevant events from incident creation. * Aggregation of multiple related events into existing SIR incidents to prevent duplication. * Bi-directional synchronization between Splunk ES notable event statuses and ServiceNow SIR incident statuses, ensuring consistent updates. ## Requirements and Compatibility * **ServiceNow AI Platform:** Installation and activation of the `com.snc.sidep` plugin and core Security Operations applications (Security Integration Framework, Security Support Common, Security Incident Response) in the specified order is required. * **ServiceNow Addons:** The ServiceNow Security Operations Event Ingestion Addon for Splunk ES is optional and only needed for manual event forwarding. * **Splunk Versions:** Tested with Splunk Enterprise version 10.0.0 and earlier, and Splunk Enterprise Security application version 8.3.0 and earlier. * **MID Server:** A configured MID Server is required for on-premises Splunk deployments to enable communication between ServiceNow and Splunk. No MID Server is needed for Splunk Cloud. ## Practical Benefits for ServiceNow Customers This integration streamlines the ingestion of security events from Splunk Enterprise Security into ServiceNow SIR, enhancing SOC efficiency by providing automated and manual options for incident creation. It enables tailored event handling through profiles and customizable field mappings, reduces incident duplication, and maintains synchronized event and incident statuses. By leveraging this integration, customers can improve threat visibility, accelerate incident response times, and maintain a robust security posture within their ServiceNow AI Platform environment. 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/oEh8SW2y0YHvcOMuL39Pew "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/TXrTKFpJjILx2FjdqPNmFg "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=brazil&pubname=brazil-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/589W_jL7CMrtTXpnB5ApBw "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.