CyberStack

MITRE ATT&CK / Techniques / T1613

Container and Resource Discovery

ID
T1613
Tactics
TA0007 Discovery
Platforms
Containers
Data sources
Pod Enumeration, Container Enumeration
Source
attack.mitre.org
MITRE last modified
25 Oct 2025

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.[6][7] In Docker, logs may leak information about the environment, such as the environment’s configuration, which services are available, and what cloud provider the victim may be utilizing. The discovery of these resources may inform an adversary’s next steps in the environment, such as how to perform lateral movement and which methods to utilize for execution.

Detection

Mitigations (3)

M1018 User Account Management

Enforce the principle of least privilege by limiting dashboard visibility to only the required users. When using Kubernetes, avoid giving users wildcard permissions or adding users to the system:masters group, and use RoleBindings rather than ClusterRoleBindings to limit user privileges to specific namespaces.[1]

M1030 Network Segmentation

Deny direct remote access to internal systems through the use of network proxies, gateways, and firewalls.

M1035 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. Require secure port access to communicate with the APIs over TLS by disabling unauthenticated access to the Docker API and Kubernetes API Server.[2][3] In Kubernetes clusters deployed in cloud environments, use native cloud platform features to restrict the IP ranges that are permitted to access to API server.[4] Where possible, consider enabling just-in-time (JIT) access to the Kubernetes API to place additional restrictions on access.[5]

Groups (1)

Software (4)

References

  1. Kubernetes RBAC
  2. Docker Daemon Socket Protect
  3. Kubernetes API Control Access
  4. Kubernetes Cloud Native Security
  5. Microsoft AKS Azure AD 2023
  6. Docker API
  7. Kubernetes API