Splunk® Enterprise Security

Release Notes

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.

Fixed Issues for Splunk Enterprise Security

The following issues have been resolved for this version of Splunk Enterprise Security.


Date resolved Issue number Description
2020-04-03 SOLNESS-21581 Entity merge not parsing MV fields in KV Store sources
2020-04-02 SOLNESS-21845 Entities merge on previous foreign keys
2020-04-02 SOLNESS-21575 A&I breaks when source lookups contain _key field
2020-03-16 SOLNESS-21907, SOLNESS-21911 Threat Intelligence Manager: Incomplete/Orphaned stanzas will cause the manager to exit
2020-03-05 SOLNESS-21951 Unable to Turn Off Acceleration Enforcement on Data Models
2020-02-04 SOLNESS-16682, SPL-170703 Internal Error: Missing a search command before *
2020-01-27 SOLNESS-21476 Notable Event Framework: Invalid severity values afflict urgency calculation
2020-01-27 SOLNESS-21222, SOLNESS-21102 Risk Framework: For risk correlation we aren't properly layering all asset keys (namely ip)
Last modified on 03 April, 2020
Release Notes for Splunk Enterprise Security   Known Issues for Splunk Enterprise Security

This documentation applies to the following versions of Splunk® Enterprise Security: 6.1.1


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