Kubernetes Pod Created in Default Namespace
The following analytic detects the creation of Kubernetes pods in the default, kube-system, or kube-public namespaces. It leverages Kubernetes audit logs to identify pod creation events within these specific…
Description
The following analytic detects the creation of Kubernetes pods in the default, kube-system, or kube-public namespaces. It leverages Kubernetes audit logs to identify pod creation events within these specific namespaces. This activity is significant for a SOC as it may indicate an attacker attempting to hide their presence or evade defenses. Unauthorized pod creation in these namespaces can suggest a successful cluster breach, potentially leading to privilege escalation, persistent access, or further malicious activities within the cluster.
Detection logic
Detection requirements
- Platform
- ContainersIaaSLinuxmacOSWindows
The rule states no platform. This is derived from the ATT&CK technique it maps to.
- Log source category
- kubernetes_audit
Known benign triggers
- No false positives have been identified at this time.
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 |
|---|---|
| kubernetes.io/docs/tasks/debug/debug-cluster/audit/ | 15 |
From the source
- At source
- Open at source
- Upstream identifier
- 3d6b1a81-367b-42d5-a925-6ef90b6b9f1e
- Tagged by the source as
- Kubernetes SecurityKubernetescloudSplunk CloudSplunk EnterpriseSplunk Enterprise Securitynetwork
Licence
- Published under
- Apache License 2.0Read the licence
- Attribution
- Required
- Obtained under
- Apache-2.0Read the origin licence
Authorship
- Written by
- Published
- Aug 26, 2026
- Version
- 1