Container and Resource Discovery T1613
Tactic: Discovery
Adversaries may attempt to discover containers and other resources that are available within a containers environment. Other resources may include images, deployments, pods, nodes, and other information such as the status of a cluster.
Events covered
1 catalog event is tagged with this technique by at least one rule.
| Provider | Event | Title |
|---|---|---|
| ESF | exec | Process Execution (Notify) |
Authoring guide
Patterns shared across the 43 rules above: which fields they filter on, what specific values they look for, and what they exclude. The catalog normalizes field names across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.
Fields filtered most (50 distinct)
The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.
Top indicator values (592 distinct)
Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique. Click a value to expand the rules under this technique that use it.
Exclusions (148 distinct)
Field/operator/value combinations excluded by rules under this technique (top-level not() clauses), sorted by how many rules exclude each. These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths. Click a value to expand the rules under this technique that exclude it.
Rules under this technique
Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.
Sigma 1 rule
Elastic 39 rules
- Container Management Utility Execution Detected via Defend for Containers
- Container Management Utility Run Inside A Container
- Direct Interactive Kubernetes API Request by Common Utilities
- Direct Interactive Kubernetes API Request by Unusual Utilities
- Direct Interactive Kubernetes API Request Detected via Defend for Containers
- DNS Enumeration Detected via Defend for Containers
- Docker Socket Enumeration
- Environment Variable Enumeration Detected via Defend for Containers
- Forbidden Direct Interactive Kubernetes API Request
- GitHub Authentication Token Access via Node.js
- Interactive Privilege Boundary Enumeration Detected via Defend for Containers
- Kubeconfig File Discovery
- Kubectl Configuration Discovery
- Kubectl Permission Discovery
- Kubectl Secrets Enumeration Across All Namespaces
- Kubectl Workload and Cluster Discovery
- Kubelet API Connection Attempt to Internal IP
- Kubelet Certificate File Access Detected via Defend for Containers
- Kubelet Pod Discovery Detected via Defend for Containers
- Kubernetes API Server Proxying Request to Kubelet
- Kubernetes Denied Service Account Request via Unusual User Agent
- Kubernetes Direct API Request via Curl or Wget
- Kubernetes Forbidden Request from Unusual User Agent
- Kubernetes Multi-Resource Discovery
- Kubernetes Potential Endpoint Permission Enumeration Attempt by Anonymous User Detected
- Kubernetes Potential Endpoint Permission Enumeration Attempt Detected
- Kubernetes Secrets List Across Cluster or Sensitive Namespaces
- Kubernetes Service Account Secret Access
- Kubernetes Suspicious Self-Subject Review via Unusual User Agent
- Potential Cluster Enumeration via jq Detected via Defend for Containers
- Potential Direct Kubelet Access via Process Arguments
- Potential Direct Kubelet Access via Process Arguments Detected via Defend for Containers
- Potential Kubectl Masquerading via Unexpected Process
- Potential Kubeletctl Execution
- Potential Kubeletctl Execution Detected via Defend for Containers
- Service Account Namespace Read Detected via Defend for Containers
- Service Account Token or Certificate Access Followed by Kubernetes API Request
- Tool Enumeration Detected via Defend for Containers
- Unusual Process Connection to Docker or Containerd Socket