GKE Forbidden Creation Request
Detects denied GKE API create requests from non-control-plane identities. Failed creates can indicate RBAC probing, stolen credentials with insufficient privileges, or attempts to deploy unauthorized workloads.
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
- Log source category
- event_index
Known benign triggers
- Developers or CI jobs with incomplete RBAC can generate denied creates. Tune after validating expected identities and namespaces. GKE control-plane and bootstrap identities are excluded.
MITRE ATT&CK mappings
Not mapped to ATT&CK.
References
| Reference | Cited by |
|---|---|
| cloud.google.com/kubernetes-engine/docs/how-to/audit-logging | 12from 2 sources |
| kubernetes.io/docs/reference/access-authn-authz/rbac/ | 9from 2 sources |
From the source
- At source
- Open at source
- Upstream identifier
- a76f049d-97fb-4058-9379-1bd985d523c2
- Tagged by the source as
- Data Source: GCPData Source: Google Cloud PlatformDomain: CloudDomain: KubernetesResources: Investigation GuideTactic: ExecutionUse Case: Threat Detection
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Aug 27, 2026
- Version
- 1