Configure asset and identity correlation in Splunk Enterprise Security
After you add your asset and identity data to Splunk Enterprise Security, configure asset and identity correlation in Splunk Enterprise Security.
- Choose whether to enable asset and identity correlation, disable it, or restrict correlation to occur only for select source types. If in doubt, keep asset and identity correlation enabled. See How asset and identity correlation works for more information about how the correlation enriches events at search time.
- From the Splunk ES menu bar, select Configure > Data Enrichment > Asset and Identity Management > Correlation Setup.
- Disable for all sourcetypes is selected by default. You can change this to Enable for all sourcetypes or Enable selectively by sourcetype.
- If you choose Enable selectively by sourcetype, type a source type and select the check box for asset and/or identity.
- Click Save.
Correlation is disabled by default when deployed from a search head deployer. Disabling asset and identity correlation completely prevents events from being enriched with asset and identity data from the asset and identity lookups. This might prevent correlation searches, dashboards, and other functionality from working as expected. Consult with Splunk Professional Services or Splunk Support before disabling asset and identity correlation.
How asset and identity correlation works
To effectively detect security intrusions, an organization must be able to correlate events in log data with specific assets and identities that may be responsible for, or affected by the intrusion. When asset and identity correlation is enabled, Splunk Enterprise Security compares indexed events with asset and identity data in the asset and identity lists to provide data enrichment and context. The comparison process uses automatic lookups. You can find information about automatic lookups in the Splunk platform documentation.
- For Splunk Enterprise, see Make your lookup automatic in the Splunk Enterprise Knowledge Manager Manual.
- For Splunk Cloud, see Make your lookup automatic in the Splunk Cloud Knowledge Manager Manual.
Asset and identity correlation enriches events with asset and identity data at search time.
- Asset correlation compares events that contain data in any of the
dvcfields against the merged asset lists for matching IP address, MAC address, DNS name, or Windows NetBIOS names. Asset correlation no longer occurs automatically against the
- Identity correlation compares events that contain data in any of the
src_userfields against the merged identity lists for a matching user or session.
- Enterprise Security adds the matching output fields to the event. For example, correlation on the asset
srcfield results in additional fields such as
Asset and identity correlation allows you to determine whether multiple events can relate to the same asset or identity. You can also perform actions on the identity and asset fields added to events to open additional searches or dashboards scoped to the specific asset or identity. For example, open the Asset Investigator dashboard on a
Verify that your asset and identity data was added to Splunk Enterprise Security
How Splunk Enterprise Security processes and merges asset and identity data
This documentation applies to the following versions of Splunk® Enterprise Security: 4.7.0, 4.7.1, 4.7.2, 4.7.3, 4.7.4, 4.7.5, 4.7.6, 5.0.0, 5.0.1, 5.1.0, 5.1.1, 5.2.0, 5.2.1, 5.2.2, 5.3.0, 5.3.1, 6.0.0, 6.0.1, 6.0.2, 6.1.0, 6.1.1, 6.2.0, 6.3.0 Cloud only, 6.4.0, 6.4.1, 6.5.0 Cloud only, 6.5.1 Cloud only, 6.6.0, 6.6.2, 7.0.0, 7.0.1, 7.0.2, 7.1.0