D023F2
Network
🌐 Honey Subnet
Fake subnets within real VPCs for scanning detection.
What it is
An unused subnet inside a real network, holding at least one decoy listener. Scanning tools sweep whole address ranges, so they inevitably touch it. Because nothing legitimate connects there, any traffic into the subnet indicates scanning or lateral movement; an empty subnet with no listener would leave no record at all.
Implementation requirements
- Create a subnet inside a real VPC or VNet, named and sized like production, that no workload uses
- Put at least one decoy listener or network interface in it. Flow logs record traffic at network interfaces, so traffic to an empty subnet leaves no record
- Monitoring: flow logs on the decoy subnet. Nothing legitimate connects there, so any flow into it is scanning or lateral movement. Flow logs arrive minutes late; a listener's own log is faster
- Safety: route tables and security rules allow inbound traffic to the decoys only, with no outbound path into production
- OPSEC: CIDR, tags and route tables consistent with neighbouring subnets
- Rollback: Delete the listener or interface, then the subnet. Remove its route-table associations.
- Upkeep: Keep it in IPAM as reserved, so nothing is assigned into it. Monthly proof-of-life scan from a test host.
Technologies
Network
ATT&CK coverage 5
| Technique | Tactic | Status | Confidence | Tier |
|---|---|---|---|---|
| T1018 Remote System Discovery |
Discovery | confirmed | strong | T1 |
| ↳ 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)
| ||||
| 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. | ||||
| T1595 Active Scanning |
Reconnaissance | confirmed | strong | T1 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (2 sources)
| ||||
| T1595.001 Scanning IP Blocks |
Reconnaissance | confirmed | strong | T1 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (3 sources)
| ||||
Evidence
- Decoy Network Resource (D3-DNR) — MITRE D3FEND standard
- A Virtual Honeypot Framework — Provos, N., USENIX Security Symposium 2004 peer-reviewed
- MITRE Engage — adversary engagement matrix and ATT&CK mapping — MITRE 2022 standard
- MITRE ATT&CK Enterprise v20.0 — MITRE 2026 standard