Detection: Kubernetes Azure detect suspicious kubectl calls

REMOVED DETECTION

This detection has been removed from the Splunk Threat Research content library and is no longer maintained or supported.

Reason: Detection deprecated as it no longer effectively identifies the intended malicious activity

Removed in version: 5.2.0

If you have any questions or concerns, please reach out to us at research@splunk.com.

Updated Date: 2026-05-13 ID: 4b6d1ba8-0000-4cec-87e6-6cbbd71651b5 Author: Rod Soto, Splunk Type: Hunting Product: Splunk Enterprise Security

Description

This search provides information on rare Kubectl calls with IP, verb namespace and object access context

Search

1`kubernetes_azure` category=kube-audit 
2| spath input=properties.log 
3| spath input=responseObject.metadata.annotations.kubectl.kubernetes.io/last-applied-configuration 
4| search userAgent=kubectl* sourceIPs{}!=127.0.0.1 sourceIPs{}!=::1 
5| table sourceIPs{} verb userAgent user.groups{} objectRef.resource objectRef.namespace requestURI 
6| rare sourceIPs{} verb userAgent user.groups{} objectRef.resource objectRef.namespace requestURI 
7|`kubernetes_azure_detect_suspicious_kubectl_calls_filter`

Data Source

No data sources specified for this detection.

Macros Used

Name	Value
kubernetes_azure	`sourcetype=mscs:storage:blob:json`
kubernetes_azure_detect_suspicious_kubectl_calls_filter	``

kubernetes_azure_detect_suspicious_kubectl_calls_filter is an empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Annotations

- MITRE ATT&CK

+ Kill Chain Phases

+ NIST

+ CIS

- Threat Actors

ID	Technique	Tactic

Default Configuration

This detection is configured by default in Splunk Enterprise Security to run with the following settings:

Setting	Value
Disabled	true
Cron Schedule	`N/A`
Earliest Time	`N/A`
Latest Time	`N/A`
Schedule Window	`N/A`
Creates Finding (Notable)	No
Creates Intermediate Finding (Risk Event)	No

Hunting detections do not generate a Finding (Notable) or Intermediate Findings (Risk Events).

Implementation

You must install the Add-on for Microsoft Cloud Services and Configure Kube-Audit data diagnostics

Known False Positives

Kubectl calls are not malicious by nature. However source IP, verb and Object can reveal potential malicious activity, specially suspicious IPs and sensitive objects such as configmaps or secrets

Associated Analytic Story

Kubernetes Sensitive Object Access Activity

Detection Testing

Test Type	Status	Dataset	Source	Sourcetype
Validation	Not Applicable	N/A	N/A	N/A
Unit	Not Applicable	N/A	`N/A`	`N/A`

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: GitHub |

Version: 4