Kubernetes Potential Enumeration Activity
Detects potential Kubernetes enumeration or attack activity via the audit log. This includes the execution of common shells, utilities, or specialized tools like 'Rakkess' (access_matrix) and 'TruffleHog' via…
Description
Detects potential Kubernetes enumeration or attack activity via the audit log. This includes the execution of common shells, utilities, or specialized tools like 'Rakkess' (access_matrix) and 'TruffleHog' via Kubernetes API requests. Attackers use these methods to perform reconnaissance (enumeration), secret harvesting, or execute code (exec) within a cluster.
Detection logic
Detection requirements
- Platform
- Containers
The rule states no platform. This is derived from the 2 ATT&CK techniques it maps to.
- Log source product
- kubernetes
- Log source service
- audit
Known benign triggers
- Authorized administrative maintenance via kubectl
- Automated internal infrastructure monitoring and certificate rotation
- Security-approved vulnerability or secret scanning in DevSecOps pipelines
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 |
|---|---|
| github.com/corneliusweig/rakkess | Only this detection cites it |
| github.com/trufflesecurity/trufflehog | 5 |
| www.nccgroup.com/research/detection-engineering-for-kubernetes-clusters/ | Only this detection cites it |
From the source
- At source
- Open at source
- Upstream identifier
- 597a7e84-187d-458b-9e4f-2f5a0e676711
- Tagged by the source as
- attack.discoveryattack.execution
Licence
- Published under
- Detection Rule License 1.1Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Aug 26, 2026
- Version
- 1