Adversaries may deploy a container into an environment to facilitate execution or evade defenses. In some cases, adversaries may deploy a new container to execute processes associated with a particular image or deployment, such as processes that execute or download malware. In others, an adversary may deploy a new container configured without network rules, user limitations, etc. to bypass existing defenses within the environment.
Containers can be deployed by various means, such as via Docker's <code>create</code> and <code>start</code> APIs or via a web application such as the Kubernetes dashboard or Kubeflow.(Citation: Docker Containers API)(Citation: Kubernetes Dashboard)(Citation: Kubeflow Pipelines) Adversaries may deploy containers based on retrieved or built malicious images or from benign images that download and execute malicious payloads at runtime.(Citation: Aqua Build Images on Hosts)
View in MITRE ATT&CK®Capability ID | Capability Description | Mapping Type | ATT&CK ID | ATT&CK Name |
---|---|---|---|---|
artifact_registry | Artifact Registry | technique_scores | T1610 | Deploy Container |
google_kubernetes_engine | Google Kubernetes Engine | technique_scores | T1610 | Deploy Container |
anthosconfigmanagement | AnthosConfigManagement | technique_scores | T1610 | Deploy Container |
binary_authorization | Binary Authorization | technique_scores | T1610 | Deploy Container |
container_registry | Container Registry | technique_scores | T1610 | Deploy Container |