Splunk® Enterprise Security

Administer Splunk Enterprise Security

Splunk Enterprise Security (ES) versions 6.0.0, 6.0.1, and 6.3.0 are no longer available for download from Splunkbase as of April 15, 2021. Please upgrade to the latest version of Splunk Enterprise Security to avoid any potential issues with Assets and Identity management.
This documentation does not apply to the most recent version of Splunk® Enterprise Security. For documentation on the most recent version, go to the latest release.

Asset and identity fields after processing in Splunk Enterprise Security

The following tables describe the fields that exist in the asset and identity lookups after Splunk Enterprise Security finishes processing the source lookup files. These fields are the fields present in the lookups that store merged asset and identity data. See Lookups that store merged asset and identity data in Splunk Enterprise Security.

The tables below list the default asset and identity fields in the KV store collections after the merge process completes. However, take note that it is possible to revise fields from multivalue to single, and tag or untag fields. It is also possible to add custom fields.

Asset fields after processing

Asset fields of the asset lookup after the saved searches perform the merge process.

Field Action taken by ETL
bunit Unchanged if configured as a single value field. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
city Unchanged if configured as a single value field. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
country Unchanged if configured as a single value field. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
dns Unchanged if configured as a single value field. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
lat Unchanged if configured as a single value field. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
long Unchanged if configured as a single value field. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
mac Unchanged if configured as a single value field. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
nt_host Unchanged if configured as a single value field. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
owner Unchanged if configured as a single value field. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
priority Unchanged if configured as a single value field. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
asset_id Generated from the values of dns, ip, mac, and nt_host fields. Accepts all values and converts them to a multivalue field.
asset_tag By default, generated from the values of category, pci_domain, is_expected, should_timesync, should_update, requires_av, and bunit fields. Also custom generated from assets that have been tagged. See Asset Settings.
category Enriched with "pci" if the value contains "cardholder". Accepts all values and converts them to a multi-value field.
ip Validates and splits the field into CIDR subnets as necessary. Accepts all values and converts them to a multi-value field.
pci_domain Enriched with "wireless, trust, untrust, cardholder, or dmz" based on configured field values. Accepts all values and converts them to a multi-value field. See Configure assets in the Splunk App for PCI Compliance Installation and Configuration Manual.
is_expected Normalized to a boolean. Accepts all values and converts them to a multivalue field.
should_timesync Normalized to a boolean. Accepts all values and converts them to a multivalue field.
should_update Normalized to a boolean. Accepts all values and converts them to a multivalue field.
requires_av Normalized to a boolean. Accepts all values and converts them to a multivalue field.
asset Generated by the ip, mac, nt_host, and dns fields after the original fields are transformed. Accepts all values and converts them to a multivalue field.
cim_entity_zone Not processed if entity zones are disabled.

Identity fields after processing

Identity fields of the identity lookup after the saved searches perform the merge process.

Field Action taken by ETL
bunit Unchanged if configured as a single value field. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
email Unchanged if configured as a single value field. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
endDate Unchanged if configured as a single value field. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
first Unchanged if configured as a single value field. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
last Unchanged if configured as a single value field. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
managedBy Unchanged if configured as a single value field. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
nick Unchanged if configured as a single value field. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
phone Unchanged if configured as a single value field. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
prefix Unchanged if configured as a single value field. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
priority Unchanged if configured as a single value field. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
startDate Unchanged if configured as a single value field. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
suffix Unchanged if configured as a single value field. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
work_city Unchanged if configured as a single value field. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
work_country Unchanged if configured as a single value field. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
work_lat Unchanged if configured as a single value field. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
work_long Unchanged if configured as a single value field. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
watchlist Normalized to a boolean. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
category Appends "pci" if the value contains "cardholder". Accepts all values and converts them to a multi-value field.
identity Generated based on values in the input row and conventions specified in the Identity Lookup Configuration. Accepts all values and converts them to a multi-value field.
identity_id Generated from the values of identity, first, last, and email. Accepts all values and converts them to a multivalue field if configured as a multivalue field.
identity_tag By default, generated from the values of bunit, category, and watchlist. Also custom generated from assets that have been tagged. See Identity Settings.
cim_entity_zone Not processed if entity zones are disabled.
Last modified on 22 November, 2021
Lookups that store merged asset and identity data in Splunk Enterprise Security   Modify asset and identity lookups

This documentation applies to the following versions of Splunk® Enterprise Security: 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


Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters