Mapping alerts and events for the Splunk Enterprise Event Ingestion integration
Summarize
Summary of Mapping alerts and events for the Splunk Enterprise Event Ingestion integration
This guide outlines how to map event fields from Splunk Enterprise to ServiceNow's Security Incident Response (SIR) platform. Users with thesnsi.adminrole can ingest sample alerts or export event data, allowing customization of fields that populate SIR security incidents.
Show less
Key Features
- Sample Alert Ingestion: Fetch sample data from Splunk to view and map alert fields.
- Customizable Mapping: Edit default mapping grids to tailor which fields correspond to SIR security incident fields.
- Field Verification: Ensure critical fields are correctly mapped by comparing the alert sample ingestion section with the mapping grid.
- Event Data Loading: Manually load event sample data from Splunk to ServiceNow using .xml files.
- Filtering and Duplication Prevention: Set filter conditions to control which alerts are ingested and to aggregate related events into a single incident, minimizing duplicates.
- Script Editor: Format Splunk field values that do not directly translate to SIR incident fields.
Key Outcomes
By effectively mapping alerts and events, ServiceNow customers can enhance their security incident management processes. This integration allows for better visibility of incoming alerts, reduces duplicate incidents, and ensures that relevant data is accurately reflected in the SIR platform, ultimately improving response times and incident handling efficiency.
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
For the mapping step, as a user with the sn_si.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 click to 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.
After you click 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, click Mapping on the progress bar.
- 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.
Manual Event forwarding profiles
After creating a profile for an event, the process flow for the configuration is shown in the following figure.
The next step is to ingest triggered alerts or export data and map values to the SIR security incident fields.