🖥️ Honey VM Instance
Decoy EC2/VM/GCE instances with realistic services.
What it is
A cloud virtual machine that looks like part of the real fleet: same image, agents and naming, exposing only the services its role implies. Attackers scanning or moving laterally treat it as one more host to try. It is a running system, so logins, flow logs and the control-plane calls that name it all show the attacker touching something nobody legitimately uses.
Implementation requirements
- AWS:
aws ec2 run-instances(or Terraformaws_instance) in a subnet where real workloads live. Azure:az vm create. GCP:gcloud compute instances create. Use the same base image, agents and tags as the real fleet - Expose only the services the instance's role implies (SSH or RDP, a web admin page). No real credentials, data or trust relationships on the host
- Monitoring, host: sshd authentication logs or Windows 4624/4625. Network: VPC or VNet flow logs for connections to the instance. Control plane: calls that name the instance, such as
ec2:GetPasswordData,ssm:StartSessionorssm:SendCommand, Azure Run Command, or a GCPsetMetadataSSH-key push. Listing every instance (DescribeInstances) does not single out the decoy - Safety: the instance profile or managed identity holds no permissions. Deny outbound traffic except to your log collector, so a compromised decoy cannot be used to attack anything
- Rebuild from a known-good image after every interaction; treat the old disk as evidence
- OPSEC: match the fleet's OS, patch level, hostname scheme and size. A lone unpatched box with nothing else like it is a honeypot tell
- Rollback: Snapshot the disk for evidence, then terminate the instance. Remove its DNS records, breadcrumbs and flow-log configuration.
- Upkeep: Patch on the fleet's schedule, so it never stands out as the one unpatched host. Monthly proof-of-life connection; rebuild from the golden image after every real touch.
Technologies
ATT&CK coverage 35
| Technique | Tactic | Status | Confidence | Tier |
|---|---|---|---|---|
| T1074 Data Staged |
Collection | theoretical | weak | T2 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (2 sources)
Staging into a defender-planted location is not documented attacker behaviour. | ||||
| T1074.002 Remote Data Staging |
Collection | theoretical | weak | T2 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (1 source)
Staging into a decoy location is not documented behaviour. | ||||
| T1105 Ingress Tool Transfer |
Command & Control | confirmed | strong | T2 |
| ↳ Detection point: seen once the attacker is working inside a high-fidelity decoy | ||||
↳ Evidence (2 sources)
| ||||
| T1212 Exploitation for Credential Access |
Credential Access | theoretical | moderate | T2 |
| ↳ Detection point: seen once the attacker is working inside a high-fidelity decoy | ||||
↳ Evidence (3 sources)
Exploitation is seen because the vulnerable-looking host is the decoy. | ||||
| T1552.005 Cloud Instance Metadata API |
Credential Access | theoretical | moderate | T2 |
| ↳ Detection point: the decoy fires at a later step of the attack | ||||
↳ Evidence (2 sources)
Not specifically through the metadata service. | ||||
| T1578 Modify Cloud Compute Infrastructure |
Defense Impairment | theoretical | moderate | T2 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (3 sources)
Moderate: behaviour and log signal are documented; no study or product shows honey instances or snapshots specifically. | ||||
| T1082 System Information Discovery |
Discovery | confirmed | strong | T2 |
| ↳ Detection point: seen once the attacker is working inside a high-fidelity decoy | ||||
↳ Evidence (2 sources)
| ||||
| T1518 Software Discovery |
Discovery | theoretical | weak | T2 |
↳ Evidence (2 sources)
Listing installed software touches no decoy. | ||||
| T1580 Cloud Infrastructure Discovery |
Discovery | theoretical | moderate | T1 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (3 sources)
Moderate: a plain List call does not name the decoy. The alert fires when the attacker queries the decoy resource itself, which the token documentation does not break down by API call. | ||||
| T1673 Virtual Machine Discovery |
Discovery | theoretical | moderate | T2 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (3 sources)
| ||||
| T1059 Command and Scripting Interpreter |
Execution | confirmed | strong | T2 |
| ↳ Detection point: seen once the attacker is working inside a high-fidelity decoy | ||||
↳ Evidence (2 sources)
| ||||
| T1059.004 Unix Shell |
Execution | confirmed | strong | T2 |
| ↳ Detection point: seen once the attacker is working inside a high-fidelity decoy | ||||
↳ Evidence (3 sources)
| ||||
| T1059.006 Python |
Execution | theoretical | moderate | T2 |
| ↳ Detection point: seen once the attacker is working inside a high-fidelity decoy | ||||
↳ Evidence (2 sources)
| ||||
| T1569 System Services |
Execution | theoretical | moderate | T2 |
| ↳ Detection point: seen once the attacker is working inside a high-fidelity decoy | ||||
↳ Evidence (2 sources)
| ||||
| T1651 Cloud Administration Command |
Execution | theoretical | moderate | T3 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (3 sources)
| ||||
| T1020.001 Traffic Duplication |
Exfiltration | theoretical | weak | T3 |
| ↳ Detection point: seen once the attacker is working inside a high-fidelity decoy | ||||
↳ Evidence (1 source)
No source shows a decoy observing traffic duplication. | ||||
| T1489 Service Stop |
Impact | theoretical | moderate | T4 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (2 sources)
Moderate: the service canary is a published prototype, not yet tested against live ransomware. | ||||
| T1496 Resource Hijacking |
Impact | confirmed | strong | T3 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (4 sources)
| ||||
| T1496.001 Compute Hijacking |
Impact | confirmed | strong | T3 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (4 sources)
| ||||
| T1499 Endpoint Denial of Service |
Impact | theoretical | weak | T1 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (1 source)
DoS against a decoy endpoint covers no real endpoint. | ||||
| T1529 System Shutdown/Reboot |
Impact | theoretical | moderate | T2 |
| ↳ Detection point: seen once the attacker is working inside a high-fidelity decoy | ||||
↳ Evidence (3 sources)
| ||||
| ↳ Detects shutdown of a decoy, not of real systems. | ||||
| T1133 External Remote Services |
Initial Access | confirmed | strong | T2 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (4 sources)
| ||||
| T1190 Exploit Public-Facing Application |
Initial Access | confirmed | strong | T2 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (5 sources)
| ||||
| T1021 Remote Services |
Lateral Movement | confirmed | strong | T2 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (2 sources)
| ||||
| T1021.008 Direct Cloud VM Connections |
Lateral Movement | theoretical | moderate | T2 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (2 sources)
Cloud-API connections to a decoy VM are logged control-plane calls. | ||||
| T1210 Exploitation of Remote Services |
Lateral Movement | theoretical | moderate | T2 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (3 sources)
| ||||
| T1563 Remote Service Session Hijacking |
Lateral Movement | theoretical | moderate | T2 |
| ↳ Detection point: seen once the attacker is working inside a high-fidelity decoy | ||||
↳ Evidence (3 sources)
| ||||
| T1098.004 SSH Authorized Keys |
Persistence | confirmed | strong | T2 |
| ↳ Detection point: seen once the attacker is working inside a high-fidelity decoy | ||||
↳ Evidence (2 sources)
| ||||
| T1133 External Remote Services |
Persistence | confirmed | strong | T2 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (2 sources)
| ||||
| T1068 Exploitation for Privilege Escalation |
Privilege Escalation | theoretical | moderate | T3 |
| ↳ Detection point: seen once the attacker is working inside a high-fidelity decoy | ||||
↳ Evidence (3 sources)
| ||||
| T1611 Escape to Host |
Privilege Escalation | confirmed | strong | T3 |
| ↳ Detection point: seen once the attacker is working inside a high-fidelity decoy | ||||
↳ Evidence (1 source)
| ||||
| T1216 System Script Proxy Execution |
Stealth | theoretical | weak | T2 |
| ↳ Detection point: seen once the attacker is working inside a high-fidelity decoy | ||||
↳ Evidence (2 sources)
Attackers use the real system script; a decoy copy is rarely touched. | ||||
| T1218 System Binary Proxy Execution |
Stealth | theoretical | weak | T2 |
| ↳ Detection point: seen once the attacker is working inside a high-fidelity decoy | ||||
↳ Evidence (2 sources)
Attackers use the real System32 binary; a decoy copy is rarely touched. | ||||
| T1497 Virtualization/Sandbox Evasion |
Stealth | theoretical | weak | T2 |
| ↳ Detection point: seen once the attacker is working inside a high-fidelity decoy | ||||
↳ Evidence (1 source)
Sandbox checks run inside the attacker's own code. | ||||
| ↳ Inverted logic (a VM that deliberately fails sandbox checks). Clever but unproven. | ||||
| T1612 Build Image on Host |
Stealth | theoretical | moderate | T2 |
| ↳ Detection point: seen once the attacker is working inside a high-fidelity decoy | ||||
↳ Evidence (2 sources)
| ||||
Evidence
- Decoy Network Resource (D3-DNR) — MITRE D3FEND standard
- Decoy Environment (D3-DE) — MITRE D3FEND standard
- A Virtual Honeypot Framework — Provos, N., USENIX Security Symposium 2004 peer-reviewed
- Agentic Cloud Decoys: A Deception-Driven Framework for Autonomous Intrusion Investigation — Manivannan, M.; Alharthi, D., arXiv:2607.24006 2026 peer-reviewed
- 2023 Honeypotting in the Cloud Report — Orca Security 2023 industry
- MITRE Engage — adversary engagement matrix and ATT&CK mapping — MITRE 2022 standard
- MITRE ATT&CK Enterprise v20.0 — MITRE 2026 standard
- Cowrie — SSH and Telnet honeypot — Oosterhof, M. (maintainer), Cowrie project (open source) practitioner
- Container Orchestration Honeypot: Observing Attacks in the Wild — Spahn, N.; Hanke, N.; Holz, T.; Kruegel, C.; Vigna, G., RAID 2023 peer-reviewed