Detection: Kubernetes GCP detect service accounts forbidden failure 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: 7094808d-432a-48e7-bb3c-77e96c894f3b Author: Rod Soto, Splunk Type: Hunting Product: Splunk Enterprise Security

Description

This search provides information on Kubernetes service accounts with failure or forbidden access status, this search can be extended by using top or rare operators to find trends or rarities in failure status, user agents, source IPs and request URI

Search

1`google_gcp_pubsub_message` system:serviceaccounts data.protoPayload.response.status.allowed!=* 
2| table src_ip src_user http_user_agent data.protoPayload.response.spec.resourceAttributes.namespace data.resource.labels.cluster_name data.protoPayload.response.spec.resourceAttributes.verb  data.protoPayload.request.status.allowed data.protoPayload.response.status.reason data.labels.authorization.k8s.io/decision 
3| dedup src_ip src_user 
4| `kubernetes_gcp_detect_service_accounts_forbidden_failure_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_service_accounts_forbidden_failure_access_filter	``

kubernetes_gcp_detect_service_accounts_forbidden_failure_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 service logs.

Known False Positives

This search can give false positives as there might be inherent issues with authentications and permissions at cluster.

Associated Analytic Story

Kubernetes Sensitive Object Access 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: 4