GKE API Request Failure Burst by User
Detects bursts of failed GKE API requests from a single user identity within a five-minute window. Repeated authorization failures across multiple actions can indicate credential stuffing, RBAC probing, or…
Description
Detects bursts of failed GKE API requests from a single user identity within a five-minute window. Repeated authorization failures across multiple actions can indicate credential stuffing, RBAC probing, or reconnaissance with stolen tokens.
Detection logic
Its licence does not clear it for publishing here
Sunturai publishes a detection's own text where the licence it arrived under has been reviewed and permits it, and Elastic License 2.0 has not. The query as its source wrote it, its canonical form and the hash that pins this revision are in the workspace record.
Detection requirements
- Platform
- Containers
The rule states no platform. This is derived from the ATT&CK technique it maps to.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| attack.mitre.org/techniques/T1613/ | 2 |
| cloud.google.com/kubernetes-engine/docs/how-to/audit-logging | 12from 2 sources |
From the source
- At source
- Open at source
- Upstream identifier
- 94556bc7-e057-4759-9e49-fa79ee366101
- Tagged by the source as
- Data Source: GCPData Source: Google Cloud PlatformDomain: CloudDomain: ContainersDomain: KubernetesNoise: UnknownPerformance: FastPlatform: GCPPlatform: KubernetesResources: Investigation GuideRule Type: ES|QLTactic: DiscoveryUse Case: Threat Detection
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Sep 23, 2026
- Version
- 4