This search provides information on Kubernetes accounts accessing sensitve objects such as configmpas or secrets
- Type: Hunting
Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Last Updated: 2020-07-11
- Author: Rod Soto, Splunk
- ID: a46923f6-36b9-4806-a681-31f314907c30
Kill Chain Phase
1 2 3 4 `google_gcp_pubsub_message` data.labels.authorization.k8s.io/reason=ClusterRoleBinding OR Clusterrole dest=apis/rbac.authorization.k8s.io/v1 src_ip!=::1 | table src_ip src_user http_user_agent data.labels.authorization.k8s.io/decision data.labels.authorization.k8s.io/reason | dedup src_ip src_user |`kubernetes_gcp_detect_sensitive_role_access_filter`
The SPL above uses the following Macros:
kubernetes_gcp_detect_sensitive_role_access_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
How To Implement
You must install splunk add on for GCP. This search works with pubsub messaging servicelogs.
Known False Positives
Sensitive role resource access is necessary for cluster operation, however source IP, user agent, decision and reason may indicate possible malicious use.
Associated Analytic story
The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.
source | version: 1