Kubernetes Abuse of Secret by Unusual User Name
The following analytic detects unauthorized access or misuse of Kubernetes Secrets by unusual user names. It leverages Kubernetes Audit logs to identify anomalies in access patterns by analyzing the source of…
Description
The following analytic detects unauthorized access or misuse of Kubernetes Secrets by unusual user names. It leverages Kubernetes Audit logs to identify anomalies in access patterns by analyzing the source of requests based on user names. This activity is significant for a SOC as Kubernetes Secrets store sensitive information like passwords, OAuth tokens, and SSH keys, making them critical assets. If confirmed malicious, this activity could lead to unauthorized access to sensitive systems or data, potentially resulting in significant security breaches and exfiltration of sensitive information.
Detection logic
Detection requirements
- Platform
- Containers
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.
Outside the enterprise matrix
References
| Reference | Cited by |
|---|---|
| kubernetes.io/docs/tasks/debug/debug-cluster/audit/ | 15 |
From the source
- At source
- Open at source
- Upstream identifier
- df6e9cae-5257-4a34-8f3a-df49fa0f5c46
- 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