T1613: Container and Resource Discovery
Tactics: Discovery. Platforms: Containers.
Adversaries may attempt to discover containers and other resources that are available within a containers environment.
MITRE's description
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. These resources can be viewed within web applications such as the Kubernetes dashboard or can be queried via the Docker and Kubernetes APIs.
Telemetry that detects it
- Container Enumeration
- Pod Enumeration
Mitigations
- Limit Access to Resource Over Network
- Limit communications with the container service to managed and secured channels, such as local Unix sockets or remote access via SSH.
- Network Segmentation
- Deny direct remote access to internal systems through the use of network proxies, gateways, and firewalls.
- User Account Management
- Enforce the principle of least privilege by limiting dashboard visibility to only the required users.
Procedure examples
- CanisterWorm has performed environment fingerprinting to identify Kubernetes clusters. CanisterWorm has also searched for Kubernetes pods using the command os.path.exists("/var/run/secrets/kubernetes.io/serviceaccount") or…
- Hildegard has used masscan to search for kubelets and the kubelet API for additional running containers.
- Peirates can enumerate Kubernetes pods in a given namespace.
- TeamPCP Cloud Stealer can identify Docker and Kubernetes environments for credentials.
5 documented uses in all. These are a sample.
MITRE ATT&CK Enterprise 19.2. © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation.