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 for Splunk Enterprise Security
Splunk Enterprise Security version 4.7.3 was released on October 20, 2017 and includes the following fixed issues.
Date resolved | Issue number | Description |
---|---|---|
2017-10-05 | SOLNESS-12420 | corrupt csv header in identities_expanded.csv |
2017-09-18 | SOLNESS-12384 | mvtruncate looks at "src" regardless of what's passed to $input$ |
2017-09-15 | SOLNESS-12060 | ES 4.5.2 Glass Tables do not load behind apache reverse proxy |
2017-09-11 | SOLNESS-12365 | Multi-value field expansion in the asset lookup (IP, DNS, or MAC fields separated by a pipe) does not work. |
2017-09-05 | SOLNESS-12253, CIM-561 | Additional Field Extractions are not working for a specific Sourcetype |
2017-08-31 | SOLNESS-12261 | ES custom search commands using chunked protocol do not work correctly on windows (failed search or truncated results) |
2017-08-24 | SOLNESS-12282 | Asset/Identity Center --> Identity Information Panel is filtering out results improperly |
2017-08-10 | SOLNESS-12271 | Threat Intel CRUD API: GET operation should not require _key value. |
2017-07-13 | SOLNESS-12194 | Adaptive Response: Email action uses wrong message parameter (should use action.email.message.alert) |
Last modified on 24 September, 2018
PREVIOUS New features for Splunk Enterprise Security |
NEXT Known issues for Splunk Enterprise Security |
This documentation applies to the following versions of Splunk® Enterprise Security: 4.7.3
Feedback submitted, thanks!