🌐 Honey VPC/VNet
Decoy virtual networks appearing as production segments.
What it is
A virtual network named and sized like a production segment and reachable from where an intruder would pivot, populated with decoy services. Attackers map and probe networks to find the next target. Nothing legitimate uses the range, so any accepted connection into it, as recorded in flow logs or by the decoys inside, is the signal.
Implementation requirements
- Create a VPC or VNet named, tagged and sized like production segments. Make it reachable from the networks an intruder would pivot from
- Security rules allow inbound traffic to the decoys and deny outbound traffic into production. Never peer it in a way that gives the decoy network a route to real systems
- Populate it with decoy services (D011, D046). An empty network has nothing to touch
- Monitoring: flow logs on the decoy network. AWS: 1-minute aggregation. Azure: VNet flow logs. GCP: VPC Flow Logs with the sampling rate set to 100%. Nothing legitimate uses the range, so any accepted flow into it is the signal. Flow logs arrive minutes late
- Control plane:
DescribeVpcslists every network and does not single out the decoy. Changes to the decoy's routes, peering or security groups are logged writes and worth alerting on - OPSEC: flow-log and tagging configuration identical to real networks
- Rollback: Delete the decoys inside, then the network and its flow logs. Remove any routes or peering created for it.
- Upkeep: Review its security rules whenever production network rules change. Monthly proof-of-life connection into the range.
Technologies
ATT&CK coverage 10
| Technique | Tactic | Status | Confidence | Tier |
|---|---|---|---|---|
| T1040 Network Sniffing |
Credential Access | theoretical | moderate | T2 |
| ↳ Detection point: the decoy fires at a later step of the attack | ||||
↳ Evidence (3 sources)
| ||||
| T1686.001 Cloud Firewall |
Defense Impairment | theoretical | moderate | |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (2 sources)
| ||||
| T1046 Network Service Discovery |
Discovery | confirmed | strong | T1 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (3 sources)
| ||||
| T1049 System Network Connections Discovery |
Discovery | theoretical | weak | T2 |
↳ Evidence (2 sources)
Listing network connections (netstat) touches no decoy and produces no per-object event. | ||||
| 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. | ||||
| 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. | ||||
| T1048 Exfiltration Over Alternative Protocol |
Exfiltration | theoretical | weak | T3 |
| ↳ Detection point: seen once the attacker is working inside a high-fidelity decoy | ||||
↳ Evidence (2 sources)
DNS or ICMP exfiltration goes to the attacker's own server; only exfiltration from inside a honey network is seen. | ||||
| T1133 External Remote Services |
Initial Access | confirmed | strong | T2 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (4 sources)
| ||||
| T1133 External Remote Services |
Persistence | confirmed | strong | T2 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (2 sources)
| ||||
| T1535 Unused/Unsupported Cloud Regions |
Stealth | theoretical | weak | T4 |
↳ Evidence (2 sources)
Attackers can operate in unused regions without touching an existing decoy. | ||||
Evidence
- Decoy Network Resource (D3-DNR) — MITRE D3FEND standard
- MITRE Engage — adversary engagement matrix and ATT&CK mapping — MITRE 2022 standard
- MITRE ATT&CK Enterprise v20.0 — MITRE 2026 standard