This documentation does not apply to the most recent version of Splunk® Security Essentials.
For documentation on the most recent version, go to the latest release.
Known issues for Splunk Security Essentials
Known issues for Splunk Security Essentials are listed on this page. If no issues appear, there are no known issues.
Splunk Security Essentials 3.7.1
| Date filed | Issue number | Description |
|---|---|---|
| 2024-09-09 | SSE-1039 | Unable to get all the data detected with automatic introspection |
| 2024-03-27 | SSE-1011 | Some custom content from the SSE 3.7.1 backup is not restored in SSE 3.8.0. |
| 2024-02-18 | SSE-980 | Data Inventory page isn't loading resources such as icons, network failures and so on. |
| 2024-02-18 | SSE-981 | Splunk Security Essentials returns an error if PYTHONHTTPSVERIFY = 1 Workaround: Set PYTHONHTTPSVERIFY=0 in '$SPLUNK_HOME/etc/splunk-launch.conf' |
| 2023-10-09 | SSE-945 | You can't add new custom content to the list of custom content from Splunk Security Essentials version 3.7.1. Workaround:
|
| 2023-08-24 | SSE-931 | Content mapping button not loading |
| 2023-05-02 | SSE-889 | Rename "Data Source Check" dashboard to "Posture Dashboards" in the UI. |
| 2022-11-03 | SSE-808 | Applying more than four filters makes the Content page unresponsive or very slow |
Last modified on 14 October, 2024
| What's new in Splunk Security Essentials | Fixed issues for Splunk Security Essentials |
This documentation applies to the following versions of Splunk® Security Essentials: 3.7.1
Download manual
Feedback submitted, thanks!