Detection: Kubernetes Azure detect suspicious kubectl calls

DEPRECATED DETECTION

This detection has been marked as deprecated by the Splunk Threat Research team. This means that it will no longer be maintained or supported. If you have any questions or concerns, please reach out to us at research@splunk.com.

Description

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

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

Name Platform Sourcetype Source Supported App
N/A N/A N/A N/A N/A

Macros Used

Name Value
kubernetes_azure sourcetype=mscs:storage:blob:json
kubernetes_azure_detect_suspicious_kubectl_calls_filter search *
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
NistCategory.DE_AE
Cis18Value.CIS_10

Default Configuration

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

Setting Value
Disabled true
Cron Schedule 0 * * * *
Earliest Time -70m@m
Latest Time -10m@m
Schedule Window auto
Creates Risk Event False
This configuration file applies to all detections of type hunting.

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

Risk Based Analytics (RBA)

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

Detection Testing

Test Type Status Dataset Source Sourcetype
Validation Not Applicable N/A N/A N/A
Unit ❌ Failing N/A N/A N/A
Integration ❌ Failing 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: 2