
Overwrite asset or identity data with entitymerge in Splunk Enterprise Security
After you add assets and identities to Splunk Enterprise Security, you can use the entitymerge
command to merge or overwrite asset or identity data based on matched foreign keys. See Add asset and identity data to Splunk Enterprise Security.
Description
Use the entitymerge
command to merge or overwrite asset or identity data based on matched foreign keys. Primarily, you use it by default in the Search Preview tab of Asset and Identity Management. You can use it manually for debugging. See Search Preview.
Syntax
entitymerge <entitymerge-target>
Required arguments
entitymerge-target
- Syntax: [asset|identity]
- Description: Required target of the entitymerge command.
Example
You can see examples of the entitymerge
command in the Search Preview tab of Asset and Identity Management.
One example is the search preview for asset_lookup_by_str, the asset table that uses string matching to enrich events:
| `add_entity_source("demo_asset_lookup","demo_assets")` | `add_entity_source("frothly_assets_2018","frothly_assets_2018")` | `add_entity_source("seckit_idm_assets_aws_ec2","frothly_aws_assets_2018")` | `add_entity_source("simple_asset_lookup","static_assets")` | table "_source","cim_entity_zone","bunit","category","city","country","dns","ip","is_expected","lat","long","mac","nt_host","owner","pci_domain","priority","requires_av","should_timesync","should_update" | `make_ip_str` | inputlookup append=T "asset_lookup_by_str" | entitymerge "asset"
PREVIOUS Asset and identity fields after processing in Splunk Enterprise Security |
NEXT Manage threat intelligence after upgrading Splunk Enterprise Security |
This documentation applies to the following versions of Splunk® Enterprise Security: 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
Feedback submitted, thanks!