Try in Splunk Security Cloud

Description

The following analytic identifies weak encryption configurations in Splunk related to TLS validation within the httplib and urllib Python libraries. It uses REST API calls to check specific configuration settings on the search head and its peers, ensuring compliance with security advisories. This activity is significant for a SOC as weak encryption can be exploited for protocol impersonation attacks, leading to unauthorized access. If confirmed malicious, attackers could intercept and manipulate data, compromising the integrity and confidentiality of the Splunk environment.

  • Type: Hunting
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
  • Datamodel: Web
  • Last Updated: 2024-05-28
  • Author: Lou Stella, Splunk
  • ID: 900892bf-70a9-4787-8c99-546dd98ce461

Annotations

ATT&CK

ATT&CK

ID Technique Tactic
T1001.003 Protocol Impersonation Command And Control
Kill Chain Phase
  • Command and Control
NIST
  • DE.AE
CIS20
  • CIS 10
CVE 


1
2
3
4
5
6
7
8
9
10
11



| rest /services/server/info 
| table splunk_server version server_roles 
| join splunk_server [
| rest /servicesNS/nobody/search/configs/conf-server/ search="PythonSslClientConfig" 
| table splunk_server sslVerifyServerCert sslVerifyServerName] 
| join splunk_server [
| rest /servicesNS/nobody/search/configs/conf-web/settings 
|  table splunk_server serverCert sslVersions] 
| rename sslVerifyServerCert as "Server.conf:PythonSSLClientConfig:sslVerifyServerCert", sslVerifyServerName as "Server.conf:PythonSSLClientConfig:sslVerifyServerName", serverCert as "Web.conf:Settings:serverCert", sslVersions as "Web.conf:Settings:sslVersions" 
| `splunk_protocol_impersonation_weak_encryption_configuration_filter`

Macros

The SPL above uses the following Macros:

:information_source: splunk_protocol_impersonation_weak_encryption_configuration_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Required fields

List of fields required to use this analytic.

  • none

How To Implement

The user running this search is required to have a permission allowing them to dispatch REST requests to indexers (The dispatch_rest_to_indexers capability). Splunk SOAR customers can find a SOAR workbook that walks an analyst through the process of running these hunting searches in the references list of this detection. In order to use this workbook, a user will need to run a curl command to post the file to their SOAR instance such as "curl -u username:password https://soar.instance.name/rest/rest/workbook_template -d @splunk_psa_0622.json". A user should then create an empty container or case, attach the workbook, and begin working through the tasks.

Known False Positives

While all of the settings on each device returned by this search may appear to be hardened, you will still need to verify the value of PYTHONHTTPSVERIFY in $SPLUNK_HOME/etc/splunk-launch.conf on each device in order to harden the python configuration.

Associated Analytic Story

RBA

Risk Score Impact Confidence Message
50.0 50 100 $splunk_server$ may not be properly validating TLS Certificates

:information_source: The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.

Reference

Test Dataset

Replay any dataset to Splunk Enterprise by using our replay.py tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

source | version: 2