GCP Kubernetes cluster pod scan detection
The following analytic identifies unauthenticated requests to Kubernetes cluster pods. It detects this activity by analyzing GCP Pub/Sub messages for audit logs where the response status code is 401, indicating…
Description
The following analytic identifies unauthenticated requests to Kubernetes cluster pods. It detects this activity by analyzing GCP Pub/Sub messages for audit logs where the response status code is 401, indicating unauthorized access attempts. This activity is significant for a SOC because it may indicate reconnaissance or scanning attempts by an attacker trying to identify vulnerable pods. If confirmed malicious, this activity could lead to unauthorized access, allowing the attacker to exploit vulnerabilities within the cluster, potentially compromising sensitive data or gaining control over the Kubernetes environment.
Detection logic
Detection requirements
- Platform
- IaaSIdentity ProviderOffice SuiteSaaS
The rule states no platform. This is derived from the ATT&CK technique it maps to.
Known benign triggers
- Not all unauthenticated requests are malicious, but frequency, User Agent, source IPs and pods will provide context.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
No references are available for this detection.
From the source
- At source
- Open at source
- Upstream identifier
- 19b53215-4a16-405b-8087-9e6acf619842
- Tagged by the source as
- Kubernetes Scanning ActivityScattered Lapsus$ HuntersGCP Kubernetes clustercloudSplunk CloudSplunk EnterpriseSplunk Enterprise Securitythreat
Licence
- Published under
- Apache License 2.0Read the licence
- Attribution
- Required
- Obtained under
- Apache-2.0Read the origin licence
Authorship
- Published
- Aug 26, 2026
- Version
- 1