Detection: Kubernetes GCP detect sensitive role access

REMOVED DETECTION

This detection has been removed from the Splunk Threat Research content library and is no longer maintained or supported.

Reason: Detection deprecated as it no longer effectively identifies the intended malicious activity

Removed in version: 5.2.0

If you have any questions or concerns, please reach out to us at research@splunk.com.

Updated Date: 2026-05-13 ID: a46923f6-36b9-4806-a681-31f314907c30 Author: Rod Soto, Splunk Type: Hunting Product: Splunk Enterprise Security

Description

This search provides information on Kubernetes accounts accessing sensitve objects such as configmpas or secrets

Search

1`google_gcp_pubsub_message` data.labels.authorization.k8s.io/reason=ClusterRoleBinding OR Clusterrole dest=apis/rbac.authorization.k8s.io/v1 src_ip!=::1  
2| table src_ip src_user http_user_agent data.labels.authorization.k8s.io/decision data.labels.authorization.k8s.io/reason 
3| dedup src_ip src_user 
4|`kubernetes_gcp_detect_sensitive_role_access_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_sensitive_role_access_filter	``

kubernetes_gcp_detect_sensitive_role_access_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

Default Configuration

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

Setting	Value
Disabled	true
Cron Schedule	`N/A`
Earliest Time	`N/A`
Latest Time	`N/A`
Schedule Window	`N/A`
Creates Finding (Notable)	No
Creates Intermediate Finding (Risk Event)	No

Hunting detections do not generate a Finding (Notable) or Intermediate Findings (Risk Events).

Implementation

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

Kubernetes Sensitive Role Activity

Detection Testing

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