Kubernetes AWS detect most active service accounts by pod
THIS IS A DEPRECATED DETECTION
This detection has been marked deprecated by the Splunk Threat Research team. This means that it will no longer be maintained or supported.
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-06-23
- Author: Rod Soto, Splunk
- ID: 5b30b25d-7d32-42d8-95ca-64dfcd9076e6
Annotations
ATT&CK
Kill Chain Phase
NIST
- DE.AE
CIS20
- CIS 10
CVE
Search
1
2
3
4
`aws_cloudwatchlogs_eks` user.groups{}=system:serviceaccounts objectRef.resource=pods
| table sourceIPs{} user.username userAgent verb annotations.authorization.k8s.io/decision
| top sourceIPs{} user.username verb annotations.authorization.k8s.io/decision
|`kubernetes_aws_detect_most_active_service_accounts_by_pod_filter`
Macros
The SPL above uses the following Macros:
kubernetes_aws_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 fields
List of fields required to use this analytic.
- _time
How To Implement
You must install splunk AWS add on and Splunk App for AWS. This search works with cloudwatch 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 |
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: 1