Splunk® Enterprise Security

Release Notes

Splunk Enterprise Security version 4.2.x is available only to Splunk Cloud subscribers.
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.

Known issues for Splunk Enterprise Security

The following are issues and workarounds for this version of Splunk Enterprise Security.

Highlighted issues

Publication date Defect number Description
4.1.0 SOLNESS-8781 When upgrading ES, any enabled correlation searches that were custom configured to skip notable event creation will revert to creating notable events by default. For example, a correlation search that creates a risk modifier or sends an email will now create a risk modifier and a notable event, or send an email and create a notable event. Workaround: Before upgrading, note enabled correlation searches that do not create notable events. Use this search:

| rest splunk_server=local count=0 /services/saved/searches search="name=\"*- Rule\"" | where disabled=0 AND action.summary_index=0 | table 'eai:acl.app',title


After upgrading, disable notable event creation for those correlation searches.
4.1.0 SOLNESS-8919 Some searches provided with Enterprise Security will not work on buckets with reduced TSIDX files. For a list of the searches, see TSIDX reduction compatibility in the Splunk Enterprise Security Installation and Upgrade Manual.
4.2.0 SOLNESS-9486 When using the Pushdown Predicates option, if a drilldown search references an evaluated field (example: src="unknown",) the replacement drilldown search will always return "No results found."
Workaround: on the drilldown results page, remove the evaluated field from the search and run it again. Example: the pushdown predicate option changes the drilldown search to:

| search (index=* OR index=_*) ((`cim_Web_indexes`) tag=web) src="unknown"

Remove the evaluated field and run the search again

| search (index=* OR index=_*) ((`cim_Web_indexes`) tag=web) (NOT src=* OR src="unknown")

Hardware prerequisites

Publication date Defect number Description
Pre-3.2
A dashboard view reports: Error in 'DistributedSearchResultsCollectionManager'. Operating system thread limit reached; search could not be run.
This is expected behavior when the max user processes ulimit is too restrictive for the current load on the Splunk environment. See "Errors about ulimit in splunkd.log" in the Splunk Enterprise Troubleshooting Manual.

Incident Review

Publication date Defect number Description
2016-10-03 SOLNESS-10538 Incident Review default time range set to "All time"
3.2.1
Immediately after upgrading Enterprise Security, the Incident Review dashboard may not display notable events. The migration process from a .csv file to the KV Store feature implements a brief wait time to initialize the system. The first time ES comes up after the post-setup restart, there is a period where Incident Review will be unusable. The dashboard will become usable in a couple minutes after the migration completes.
Pre-3.2 SOLNESS-2508 The Incident Review dashboard feature does not work on the Solaris operating system.
Pre-3.2 SOLNESS-5072 The maximum number of notable events displayed for editing is 1000, regardless of the filter options or total number of notable events. This is the expected behavior set by default in the limits.conf setting max_events_per_bucket, and can be changed as required.
2016-06-09 SOLNESS-8167 When sorting notable events by Urgency, if the total number of notable events on the page exceeds 1000 some notable events will not be displayed.
Workaround: Change the limits.conf setting max_events_per_bucket default to a value greater then 1000.
2014-11-19 SOLNESS-5676 The Create Notable Event workflow action may result in a truncated notable event with missing fields.
2015-01-15 SOLNESS-6054 The format of Incident Review audit data has been optimized. To review Incident Review audit events created prior to ES 3.2.1, update your audit search as needed and add the latest extractions. Example:
index=_audit sourcetype=incident_review |  rex  field=_raw "^(?<end_time>[^,]*),(?<rule_id>[^,]*),(?<owner>[^,]*),(?<urgency>[^,]*),(?<status>[^,]*),(?<comment>[^,]*),(?<user>[^,]*),(?<rule_name>[^,]*)"
3.2.1 SOLNESS-7415 The list of users that can be assigned a notable event may be incomplete if ES is accessed using SAML authentication. To see a full list of users that can be assigned a notable event, wait 10 minutes after logging in for the list of users to be refreshed.
4.1.0 SOLNESS-8345 "Edit All Matching Events" gets a timeout error when trying to edit a large number of events.
Workaround: Increase the splunkdConnectionTimeout value from the default of 30 seconds in web.conf.
4.2.0 SOLNESS-9391 Notable events created on assets/identity investigator are missing link back to investigator page

Installation and Upgrade

Publication date Defect number Description
2016-05-06 SOLNESS-9227 After completing the upgrade of Enterprise Security, the Correlation Search Editor can display configurations inconsistent with pre-upgrade settings if the search migration process is still running. To review the status of the migration operation, search:

index=_internal sourcetype=configuration_check file="confcheck_es_modactions*" migrated

and look for successfully migrated searches.
Pre-3.2 CIM-169 After installing the Enterprise Security app, the splunkd.log displays a warning message:
WARN LineBreakingProcessor - Truncating line because limit of 10000 bytes has been exceeded with a line length >= 13359 - data_source="/opt/splunk/var/log/splunk/remote_searches.log", data_host="*", data_sourcetype="splunkd_remote_searches"

Workaround: Disable truncation on the indexers using the props.conf:
[splunkd_remote_searches]
TRUNCATE = 0

Configuration

Publication date Defect number Description
2016-10-03 SOLNESS-10551 Incident Review Suppressions page has no Enable / Disable links.
2016-06-10 SOLNESS-9571
The "pushdown predicates" setting does not affect drilldown searches when the `datamodel` macro is not followed by `drop_dm_object_name`
2016-05-23 SOLNESS-9420
Extreme search causing multiple core dump files
Workaround: Filter results where the size is zero. Edit the problematic context gen search in the configuration file or on the Content Management page to include |where size > 0. For example:
| tstats `summariesonly` dc(All_Traffic.src) as src_count from datamodel=Network_Traffic by _time span=30m | stats count, median(src_count) as median, stdev(src_count) as size | where size>0 | xsupdateddcontext name=src_count_30m container=network_traffic terms="minimal,low,medium,high,extreme" type=median_centered width=3 app=SA-NetworkProtection scope=app | stats count

2016-03-15 SOLNESS-8868 Guided Correlation Search editor: aggregates can overwrite each other (Stats view)
2016-09-08 SOLNESS-10340
Edits to a correlation search are not saved after upgrading ES
Workaround: Clear the browser cache before making changes to correlation searches.
2015-04-15 SOLNESS-6641 A search name containing a German umlaut cannot be opened in the Edit Correlation Search view. The JS console reports: Failed to load resource: the server responded with a status 500 (Internal Server Error)..
Pre-3.2 SOLNESS-6900 Correlation search names cannot be longer than 80 characters long. This is expected behavior.

Dashboards and Reports

Publication date Defect number Description
2016-10-03 SOLNESS-10549 Identity_Management.Expired_User_Activity object does not take the _time of the event into account.
4.1.0 SOLNESS-8665 Not all drill down links included for UBA Anomalies are valid for Splunk UBA version 2.1.2.
4.1.0 SOLNESS-8721 Files attached to an unsaved Note are stored in the KV Store before the user saves the note to the investigation.
Pre-3.2
When using a drilldown from any dashboard panel, the drilldown displays results slower than the dashboard. This is expected behavior. A drilldown runs a historical search across all indexed events mapped to the data model, where the dashboard view uses only accelerated data model objects for a faster visual response.
Pre-3.2 SOLNESS-3536 In any Individual Reports window, selecting a real-time Time Range such as: 24 hour window, 30 minute window, etc. will cause a display error:

Error in 'tstats' command: This command is not supported in a real-time search.
Workaround: Use a relative "Time Range" such as: Last 24 hours or Last 15 minutes.

Pre-3.2 SOLNESS-4387 When adding a report to a custom dashboard in Enterprise Security, the report's drilldown search may not produce the desired behavior. This includes predefined reports included with Enterprise Security. The drilldown behavior is dependent on the structure of the search, and the search commands being used.
As a workaround, you can test all report drilldown behaviors on custom dashboards, and use Simple XML to define the drilldown search for each report as desired.
Pre-3.2 SOLNESS-4631 When using Advanced Threat dashboards, some dashboard views display a yellow warning sign triangle even if the view displays results. The warning reports:
Empty csv lookup file (contains only a header) for table 'ppf_http_category': /splunk/etc/apps/DA-ESS-NetworkProtection/lookups/ppf_http_user_agent.csv
Empty csv lookup file (contains only a header) for table 'ppf_url_length': /splunk/etc/apps/DA-ESS-NetworkProtection/lookups/ppf_new_domains.csv

This is expected behavior and is harmless. The lookup files referenced in the warning message manages the per-panel filtering feature in Enterprise Security. Per-panel filtering is used to filter or whitelist items out of dashboard views that are deemed unimportant or non-threatening.

Until the per-panel filter lookup is used, the file is empty and contains only a header. This status does not affect the functioning of the dashboard panel. For more information, see "Edit the Per-Panel Filter list" in the Enterprise Security User Manual.

4.2.0 SOLNESS-9676 Timeline: Cannot highlight or select text

Inputs

Publication date Defect number Description
2015-12-28 SOLNESS-7659 The libtaxii library used by Enterprise Security does not support authenticated proxies. As a workaround, use an unauthenticated proxy if possible.
2016-08-04 SOLNESS-10052
lxml out-of-memory condition when parsing large TAXII feed documents
Workaround: Change the earliest time for the TAXII feed to pull documents with less information, or the maxsize parameter for the threat intelligence manager to allow for a larger byte size of documents in the DA-ESS-ThreatIntelligence/local/inputs.conf file. For example:
[threatlist://hailataxii_torexit]
description = Hail a TAXII.com TOR LIST
disabled = false
interval = 86400
post_args = collection="blutmagie_de_torExits" earliest="-1y" taxii_username="guest" taxii_password="guest" earliest="-1w"
type = taxii
url = http://hailataxii.com/taxii-data
[threat_intelligence_manager://sa_threat_local]
directory = $SPLUNK_HOME/etc/apps/SA-ThreatIntelligence/local/data/threat_intel
disabled  = true
maxsize   = 52428800
sinkhole  = false

Last modified on 12 October, 2016
Fixed issues for Splunk Enterprise Security   How to find answers and get help with Splunk Enterprise Security

This documentation applies to the following versions of Splunk® Enterprise Security: 4.2.1 Cloud only


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