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.
Download topic as PDF
Fixed Issues
The following issues have been resolved for this version of Splunk Enterprise Security.
Issue number | Description |
---|---|
SOLNESS-8772 | App Import updater not running on standalone systems. |
SOLNESS-8681 | Log files from custom scripts not source typed correctly. |
SOLNESS-8626 | When importing asset or identity information, finding a NULL byte character prevents further record imports. |
SOLNESS-8612 | Using unicode characters when creating a notable event in the New Notable Event UI breaks the notable event Urgency. |
SOLNESS-8568 | App Import list instability on SHC installations |
SOLNESS-8552 | Key indicators fail to load on iOS due to 10 second timeout |
SOLNESS-8550 | Datamodel audit window should indicate that retention==0 means "all time" |
SOLNESS-8480 | Threat Intelligence: Set HTTPS as default for OOTB threatlists where possible. |
SOLNESS-8463 | Users that are not members of the Admin role should be informed that they cannot perform the ES setup |
SOLNESS-8433 | A non-admin should not be able to navigate an incomplete ES installation |
SOLNESS-8369 | Users that are not members of the Admin role should not be able to use the CLI install command essinstall
|
SOLNESS-8252 | js charting issue with reports |
SOLNESS-8243 | App Import list instability on SHC installations |
SOLNESS-8214 | Authentication to a proxy when fetching a TAXII feed is failing |
SOLNESS-8019 | Threat Intel: Deprecation warnings from STIX libraries propagating to splunkd.log |
Last modified on 28 March, 2016
PREVIOUS Release Notes for Splunk Enterprise Security |
NEXT Known Issues |
This documentation applies to the following versions of Splunk® Enterprise Security: 4.1.0
Feedback submitted, thanks!