Detection: Kubernetes GCP detect most active service accounts by pod

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.

Updated Date: 2024-10-17 ID: 7f5c2779-88a0-4824-9caa-0f606c8f260f Author: Rod Soto, Splunk Type: Hunting Product: Splunk Enterprise Security

Description

This search provides information on Kubernetes service accounts,accessing pods by IP address, verb and decision

1`google_gcp_pubsub_message`  data.protoPayload.request.spec.group{}=system:serviceaccounts 
2| table src_ip src_user http_user_agent data.protoPayload.request.spec.nonResourceAttributes.verb data.labels.authorization.k8s.io/decision data.protoPayload.response.spec.resourceAttributes.resource 
3| top src_ip src_user http_user_agent data.labels.authorization.k8s.io/decision data.protoPayload.response.spec.resourceAttributes.resource 
4|`kubernetes_gcp_detect_most_active_service_accounts_by_pod_filter`

Data Source

No data sources specified for this detection.

Macros Used

Name Value
google_gcp_pubsub_message sourcetype="google:gcp:pubsub:message"
kubernetes_gcp_detect_most_active_service_accounts_by_pod_filter search *
kubernetes_gcp_detect_most_active_service_accounts_by_pod_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 splunk GCP add on. This search works with pubsub messaging service logs

Known False Positives

Not all service accounts interactions are malicious. Analyst must consider IP, verb and decision context when trying to detect maliciousness.

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