MITRE ATT&CK T1610: Deploy Container
When to use this skill
Use this skill when the task involves T1610, Deploy Container, enterprise ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK technique.
Technique context
- ATT&CK domain: enterprise
- ATT&CK ID: T1610
- Technique name: Deploy Container
- Type: technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1610
- Tactics: execution
- Platforms: Containers
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
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. In Kubernetes environments, an adversary may attempt to deploy a privileged or vulnerable container into a specific node in order to Escape to Host and access other containers running on the node. (Citation: AppSecco Kubernetes Namespace Breakout 2020)
Containers can be deployed by various means, such as via Docker's create and start APIs or via a web application such as the Kubernetes dashboard or Kubeflow. (Citation: Docker Container)(Citation: Kubernetes Dashboard)(Citation: Kubeflow Pipelines) In Kubernetes environments, containers may be deployed through workloads such as ReplicaSets or DaemonSets, which can allow containers to be deployed across multiple nodes.(Citation: Kubernetes Workload Management) 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)
Agent workflow
- Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.
- Load bundled resources as needed: use
references/technique-profile.json for structured metadata, references/detection-and-mitigation.md for triage and telemetry guidance, references/known-threat-context.md for ATT&CK relationship context, and templates/ for repeatable outputs.
- Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.
- Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.
- Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.
- Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.
Bundled resources
references/technique-profile.json: machine-readable ATT&CK metadata for this technique.
references/detection-and-mitigation.md: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.
references/known-threat-context.md: ATT&CK relationship context with attribution cautions.
templates/detection-brief.md: detection engineering brief template.
templates/hunt-plan.md: threat hunt plan template.
templates/incident-response-note.md: incident response note template.
templates/coverage-assessment.md: ATT&CK coverage assessment template.
scripts/render_brief.py: local helper that renders a Markdown defensive brief from technique-profile.json.
assets/output-schema.json: JSON schema for structured technique analysis outputs.
To generate a quick brief, run python scripts/render_brief.py --output brief.md from inside this skill directory, or adapt the templates directly.
Detection guidance
No ATT&CK detection guidance was present in the source STIX object.
Useful telemetry and data sources
- Not specified in the STIX object.
Mitigations to consider
- Audit
- Limit Access to Resource Over Network
- Network Segmentation
- User Account Management
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- Doki (malware)
- Kinsing (malware)
- Peirates (tool)
- TeamTNT (intrusion-set)
Recommended output pattern
When responding with this skill, structure the answer as:
- Assessment: whether the evidence supports this ATT&CK mapping and why.
- Evidence: specific indicators, logs, behaviors, and assumptions.
- Detection: telemetry sources, analytic logic, and tuning considerations.
- Response: containment, eradication, recovery, and validation actions.
- Coverage gaps: missing logs, sensors, controls, or environmental details.
- References: include the ATT&CK URL and any user-provided evidence references.
ATT&CK contributors
- Alfredo Oliveira, Trend Micro
- Ariel Shuper, Cisco
- Center for Threat-Informed Defense (CTID)
- Idan Frimark, Cisco
- Joas Antonio dos Santos, @C0d3Cr4zy
- Magno Logan, @magnologan, Trend Micro
- Pawan Kinger, @kingerpawan, Trend Micro
- Vishwas Manral, McAfee
- Yossi Weizman, Azure Defender Research Team
1---2name: attack-ent-t1610-deploy-container3description: "Analyze MITRE ATT&CK T1610 Deploy Container in the enterprise matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1610, Deploy Container, or enterprise ATT&CK. Adversaries may deploy a container into an environment to facilitate execution or evade defenses."4license: MITRE ATT&CK Terms of Use apply to ATT&CK-derived content. See https://attack.mitre.org/resources/terms-of-use/5metadata:6 source: https://skillmd.com/skills/santosomar/attack-ent-t1610-deploy-container7 upstream: mitre-attack/attack-stix-data8 domain: enterprise9 attack_id: T161010 attack_stix_id: attack-pattern--56e0d8b8-3e25-49dd-9050-3aa252f5aa9211 attack_version: "2.0"12 attack_modified: "2026-04-15T19:59:11.024Z"13---1415# MITRE ATT&CK T1610: Deploy Container1617## When to use this skill1819Use this skill when the task involves T1610, Deploy Container, enterprise ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK technique.2021## Technique context2223- ATT&CK domain: enterprise24- ATT&CK ID: T161025- Technique name: Deploy Container26- Type: technique27- ATT&CK URL: https://attack.mitre.org/techniques/T161028- Tactics: execution29- Platforms: Containers30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries 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. In Kubernetes environments, an adversary may attempt to deploy a privileged or vulnerable container into a specific node in order to [Escape to Host](https://attack.mitre.org/techniques/T1611) and access other containers running on the node. (Citation: AppSecco Kubernetes Namespace Breakout 2020)3738Containers 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 Container)(Citation: Kubernetes Dashboard)(Citation: Kubeflow Pipelines) In Kubernetes environments, containers may be deployed through workloads such as ReplicaSets or DaemonSets, which can allow containers to be deployed across multiple nodes.(Citation: Kubernetes Workload Management) 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)3940## Agent workflow41421. Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.432. Load bundled resources as needed: use `references/technique-profile.json` for structured metadata, `references/detection-and-mitigation.md` for triage and telemetry guidance, `references/known-threat-context.md` for ATT&CK relationship context, and `templates/` for repeatable outputs.443. Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.454. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.465. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.476. Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.4849## Bundled resources5051- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.52- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.53- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.54- `templates/detection-brief.md`: detection engineering brief template.55- `templates/hunt-plan.md`: threat hunt plan template.56- `templates/incident-response-note.md`: incident response note template.57- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.58- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.59- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.6061To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.6263## Detection guidance6465No ATT&CK detection guidance was present in the source STIX object.6667## Useful telemetry and data sources6869- Not specified in the STIX object.7071## Mitigations to consider7273- Audit74- Limit Access to Resource Over Network75- Network Segmentation76- User Account Management7778## Known threat context7980Use these examples only as contextual leads, not as proof that an observed event is this technique:8182- Doki (malware)83- Kinsing (malware)84- Peirates (tool)85- TeamTNT (intrusion-set)8687## Recommended output pattern8889When responding with this skill, structure the answer as:9091- Assessment: whether the evidence supports this ATT&CK mapping and why.92- Evidence: specific indicators, logs, behaviors, and assumptions.93- Detection: telemetry sources, analytic logic, and tuning considerations.94- Response: containment, eradication, recovery, and validation actions.95- Coverage gaps: missing logs, sensors, controls, or environmental details.96- References: include the ATT&CK URL and any user-provided evidence references.9798## ATT&CK contributors99100- Alfredo Oliveira, Trend Micro101- Ariel Shuper, Cisco102- Center for Threat-Informed Defense (CTID)103- Idan Frimark, Cisco104- Joas Antonio dos Santos, @C0d3Cr4zy105- Magno Logan, @magnologan, Trend Micro106- Pawan Kinger, @kingerpawan, Trend Micro107- Vishwas Manral, McAfee108- Yossi Weizman, Azure Defender Research Team