Try in Splunk Security Cloud

Description

The following analytic detects unauthorized attempts to reload Splunk KV Store collections via the REST API. It leverages internal index logs to identify POST requests to the /servicesNS/nobody/search/admin/collections-conf/_reload endpoint, focusing on status codes starting with '2'. This activity is significant as it may indicate improper permission handling, potentially leading to unauthorized deletion of KV Store collections. If confirmed malicious, this could result in data loss or unauthorized data manipulation, impacting the integrity and availability of critical Splunk data.

  • Type: Hunting

  • Product: Splunk Enterprise, Splunk Cloud

  • Last Updated: 2024-05-10
  • Author: Rod Soto, Eric McGinnis, Chase Franklin
  • ID: 8f0e8380-a835-4f2b-b749-9ce119364df0

Annotations

ATT&CK

ATT&CK

ID Technique Tactic
T1548 Abuse Elevation Control Mechanism Privilege Escalation, Defense Evasion
Kill Chain Phase
  • Exploitation
NIST
  • DE.AE
CIS20
  • CIS 10
CVE 


1
2
3
4
5



`splunkda` uri=/servicesNS/nobody/search/admin/collections-conf/_reload status=2* method="POST" user=* file=_reload 
| stats count min(_time) as firstTime max(_time) as lastTime values(status) as status by host clientip file method 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `splunk_enterprise_kv_store_incorrect_authorization_filter`

Macros

The SPL above uses the following Macros:

:information_source: splunk_enterprise_kv_store_incorrect_authorization_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.

  • uri
  • status
  • method
  • file
  • clientip
  • host

How To Implement

Requires access to internal indexes and REST API enabled instances.

Known False Positives

This is a hunting search and will produce false positives. Operator must follow results into instances where curl requests coming from actual users may indicate intent of exploitation.

Associated Analytic Story

RBA

Risk Score Impact Confidence Message
25.0 50 50 Possible attempt to access KV Store collections at $host$

: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