D030F2
Orchestration
🏗️ Honey CloudFormation Stack
Decoy IaC stacks for infra recon detection.
What it is
An infrastructure-as-code stack named like core infrastructure that deploys only decoy resources. Attackers read stack templates to learn how an environment is built and where its secrets live. Reading the decoy template, or changing or deleting the stack, are logged events that name it.
Implementation requirements
- AWS: a CloudFormation stack (or an equivalent Terraform state or Azure deployment) named like core infrastructure, deploying only decoy resources (D015, D020)
- Monitoring:
GetTemplateandGetTemplateSummaryon the decoy stack are read events that name it.UpdateStack,DeleteStackand drift operations on it are logged writes.DescribeStackslists every stack and does not single out the decoy - Template parameters and outputs can point to honeytokens, so the template becomes a breadcrumb (D040)
- Safety: the stack's service role can only manage the decoy resources. OPSEC: tags, stack policy and update history like real stacks
- Rollback: Delete the stack, which removes its decoy resources. Delete the stack's service role.
- Upkeep: Update the template occasionally, so its history looks alive. Quarterly proof-of-life
GetTemplate.
Technologies
AWSAzure
ATT&CK coverage 4
| Technique | Tactic | Status | Confidence | Tier |
|---|---|---|---|---|
| T1526 Cloud Service Discovery |
Discovery | theoretical | moderate | T1 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (3 sources)
Moderate: discovering that a service exists does not necessarily touch a decoy resource in it. | ||||
| 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. | ||||
| T1651 Cloud Administration Command |
Execution | theoretical | moderate | T3 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (3 sources)
| ||||
| T1490 Inhibit System Recovery |
Impact | theoretical | moderate | T4 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (2 sources)
Moderate: behaviour and log signal are documented; no study or product shows honey snapshots specifically. | ||||
Evidence
- Decoy Object (D3-DO) — MITRE D3FEND standard
- MITRE ATT&CK Enterprise v20.0 — MITRE 2026 standard
- MITRE Engage — adversary engagement matrix and ATT&CK mapping — MITRE 2022 standard