Mapping alerts and events for the Splunk Enterprise Event Ingestion integration

  • Release version: Zurich
  • Updated March 12, 2026
  • 3 minutes to read
    • Summarize
    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 Mapping alerts and events for the Splunk Enterprise Event Ingestion integration

    This integration enables ServiceNow customers to ingest and map alerts and events from Splunk Enterprise into the ServiceNow AI Platform Security Incident Response (SIR) application. This process ensures that Splunk alert and event data populate the corresponding fields within SIR security incidents, allowing for effective incident management and response.

    Show full answer Show less

    Users with the snsi.ingestionprofileadmin role perform the mapping by ingesting sample alerts or exporting event data from Splunk Enterprise. A default mapping grid is provided and can be customized to suit your organization's incident handling needs.

    Mapping Process and Key Features

    • Fetch Sample Data: Automatically ingest sample alerts from Splunk to populate alert fields on the mapping form, enabling you to see how data maps to SIR incident fields.
    • Manual Event Forwarding: Export event sample data as XML from Splunk and import it into ServiceNow for mapping.
    • Customizable Mapping Grid: Drag and drop Splunk alert fields to map them to SIR incident fields. You can add or remove mapped fields and use color coding to track duplicates or missed fields.
    • Filter Conditions: Define criteria to control which alerts are ingested or filtered out, helping streamline incident creation.
    • Incident Aggregation: Set rules to aggregate related alerts into existing incidents, reducing duplicate or overlapping security incidents.
    • Script Editor: Use scripting to format or translate Splunk event values that don’t directly match SIR incident fields—for example, mapping different malware alert types to a unified category.

    Configuration Workflows

    The integration supports two profile types with distinct configuration flows:

    • Scheduled Alert Profiles: Define recurring alert ingestion schedules, followed by mapping and filtering configuration.
    • Manual Event Forwarding Profiles: Configure manual export and ingestion of event data, then map event fields accordingly.

    After creating the profiles, the next step is to ingest triggered alerts or export event data and perform field mapping to align Splunk data with SIR security incident fields.

    After you identify the sources for scheduled alert ingestion or manual event forwarding, the next step is to map individual event fields to the fields on a ServiceNow AI Platform Security Incident Response (SIR) security incident.

    Overview of Mapping alerts and events

    For the mapping step, as a user with the sn_si.ingestion_profile_admin role, you ingest sample alerts from your Splunk Enterprise console, or you export event data for a Splunk Enterprise event.

    The following figures are examples of the default mapping grids that are provided for each type of event profile. This default mapping can be edited. This modification allows you to customize the fields that populate the security incident. With the mapping step, you can visualize how adding or removing event fields impacts the SIR security incident field values.

    Select the Alert Name, and after you select Fetch Sample Data, the Splunk alert field values are populated on the left side of the form when sample alerts are ingested by the profile. These are the Splunk alert fields that you map to the SIR security incident fields.

    Figure 1. Default mapping form for alerts
    Default mapping form for alerts.

    After you select to load attachment data for forwarded events, the Splunk event fields are populated on the left side of the form. These are the Splunk data fields that are mapped to the SIR security incident fields.

    You may prefer to review a few sample alerts on your Splunk console to ingest for the field mapping configuration step. This step is labeled, Mapping on the progress bar. If this page is not displayed, select Mapping on the progress bar.

    Mapping alerts and exporting events on-demand from your Splunk enterprise console includes the following concepts and tasks:
    • Fetch Sample data for automatically ingested alert profiles. After data is fetched (pulled) from a fired alert on the Splunk Enterprise console, available alert fields and their corresponding values are displayed in a default mapping layout on the left side of the mapping form. Tabs are displayed for you to view the values for an alert ID that you pulled. Verify that all the critical fields from the Alert Sample Ingestion section on the left of the form are mapped to the grid on the right of the form.
    • If required, load event sample data for any manually forwarded event profiles. Sample data for these events is exported in a .xml file from the Splunk Enterprise console and loaded into your ServiceNow AI Platform® instance. The imported data is displayed in the Alert Sample Ingestion section on the left of the form.
    • Edit the mapping configuration by dragging alerts from the left side and dropping them on the mapping grid on the right. The mapping grid on the right associates the incoming alert field with an outgoing security incident field.
    • Customize the mapping grid by adding or removing fields. Track overlooked or duplicated fields with the color coding that is provided.
    • Set filter conditions so that you can specify which alerts are ingested into the SIR application, and which alerts are filtered out.
    • Define additional incident field criteria that aggregates an incoming alert to an existing SIR security incident to prevent duplicate incidents. This additional filtering can reduce the number of active, overlapping security incidents by placing all related security event data on a single security incident.
    • In certain cases, event field values in the Splunk Enterprise console may not translate directly to the fields on the SIR security incident. For these values, you can use a script editor to format field values on the security incident during the mapping step. Use the script editor if you want to format values that are similar, but not identical. For example, with the script editor, the Malware Alert and Virus Infection field values in the Splunk console both translate to Malicious Code Activity in the Category field on the SIR security incident.

    Scheduled alert profiles

    After creating a scheduled alert profile, the process flow for the configuration is shown in the following figure.

    Figure 2. Process flow for scheduled alert profiles
    Process flow for scheduled alert.

    Manual Event forwarding profiles

    After creating a profile for an event, the process flow for the configuration is shown in the following figure.

    Figure 3. Process flow for event profiles
    Process flow for event export.

    The next step is to ingest triggered alerts or export data and map values to the SIR security incident fields.