UBA - Garbled characters from the events sent from UBA to Splunk

Available Languages

Updated:September 29, 2026
Document ID:SPLK045444

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Applicability

Splunk Enterprise

Description

A Splunk Admin followed the steps mentioned in the below documentation to send UBA anomalies and threats to Splunk but was seeing garbled characters when searching for events sent by UBA.

https://docs.splunk.com/Documentation/UBA/5.0.5/Integration/PushUBAContenttoES#Configure_the_Splunk_platform_to_receive_data_from_the_Splunk_UBA_output_connector


Investigation

Splunk side should display "SSL" messages as mentioned in the documentation. 
11-07-2019 15:07:42.661 -0800 INFO  TcpInputProc - Creating raw Acceptor for IPv4 port 10008 with SSL
However, user was seeing "Non-SSL" instead of "SSL" messages in splunkd.log.
INFO  TcpInputProc - Creating raw Acceptor for IPv4 port 10008 with Non-SSL

Resolution

Ther were using Splunk 8.0.4 and they were hitting below SPL-199494 which has been fixed in 8.0.9.
https://docs.splunk.com/Documentation/Splunk/8.0.9/ReleaseNotes/Fixedissues 
2021-02-09 SPL-199494, SPL-198714 tcp-ssl input stanza individual ssl certificates not working as documented
To work around the issue in 8.0.4, they changed their SPLUNK_HOME/etc/apps/Splunk_TA_ueba/local/inputs.conf to below content and then restarted their Splunk instance.
[tcp-ssl:10008]
listenOnIPv6 = no
index = ueba
sourcetype = ueba[SSL]
serverCert = /opt/splunk/etc/auth/server.pem
sslPassword = password

Then followed again the steps mentioned "Perform the following tasks on the Splunk UBA management server:" of below documentation to fix current issue.

https://docs.splunk.com/Documentation/UBA/5.0.5/Integration/PushUBAContenttoES#Configure_the_Splunk_platform_to_receive_data_from_the_Splunk_UBA_output_connector


https://docs.splunk.com/Documentation/UBA/5.0.5/Integration/PushUBAContenttoES#Configure_the_Splunk_platform_to_receive_data_from_the_Splunk_UBA_output_connector
https://docs.splunk.com/Documentation/Splunk/8.0.9/ReleaseNotes/Fixedissues

Revision History

Revision Publish Date Comments
1.0
29-Sep-2026
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products

Related Articles