Kubernetes GCP detect most active service accounts by pod
Description
This search provides information on Kubernetes service accounts,accessing pods by IP address, verb and decision
- Type: Hunting
-
Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Last Updated: 2020-07-10
- Author: Rod Soto, Splunk
- ID: 7f5c2779-88a0-4824-9caa-0f606c8f260f
Annotations
ATT&CK
Kill Chain Phase
- Exploitation
NIST
CIS20
CVE
Search
1
2
3
4
`google_gcp_pubsub_message` data.protoPayload.request.spec.group{}=system:serviceaccounts
| 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
| top src_ip src_user http_user_agent data.labels.authorization.k8s.io/decision data.protoPayload.response.spec.resourceAttributes.resource
|`kubernetes_gcp_detect_most_active_service_accounts_by_pod_filter`
Macros
The SPL above uses the following Macros:
Note that kubernetes_gcp_detect_most_active_service_accounts_by_pod_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
Required field
- _time
How To Implement
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
RBA
Risk Score | Impact | Confidence | Message |
---|---|---|---|
25.0 | 50 | 50 | tbd |
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: 1