D038F2
Config
⚙️ Honey Policy Document
Decoy IAM/resource policies.
What it is
A customer-managed policy with an attractive name, such as break-glass or admin, attached to nothing. Attackers read policies to plan privilege escalation and attach powerful ones to identities they control. Targeted reads of the decoy policy are logged, and any attempt to attach it is a strong signal.
Implementation requirements
- AWS: a customer-managed IAM policy with an attractive name (break-glass, admin) attached to nothing. Azure and GCP: a custom role definition (see D001)
- Monitoring: targeted reads (
iam:GetPolicy,iam:GetPolicyVersionon the decoy ARN) are read-only management events. Trails record them by default; EventBridge rules need theENABLED_WITH_ALL_CLOUDTRAIL_MANAGEMENT_EVENTSstate to match them - Strongest signal: any attempt to attach it (
AttachRolePolicy,AttachUserPolicy,AttachGroupPolicynaming the decoy ARN) - Known limit: bulk enumeration (
GetAccountAuthorizationDetails) returns every policy in one call and does not single out the decoy - Safety: never attach it to a real principal. If it must appear in use, attach it to a decoy principal with no credentials. OPSEC: version history and description like real policies
- Rollback: Delete the policy, after confirming it is attached to nothing.
- Upkeep: Add a new version occasionally, so it looks maintained. Quarterly proof-of-life
GetPolicyVersion.
Technologies
AWSAzureGCP
ATT&CK coverage 9
| Technique | Tactic | Status | Confidence | Tier |
|---|---|---|---|---|
| T1685 Disable or Modify Tools |
Defense Impairment | theoretical | moderate | |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (3 sources)
| ||||
| T1201 Password Policy Discovery |
Discovery | theoretical | weak | T2 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (1 source)
Password policy is domain-wide; reading a decoy policy document is T1083/T1039, not policy discovery. | ||||
| T1538 Cloud Service Dashboard |
Discovery | theoretical | moderate | T1 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (3 sources)
| ||||
| T1651 Cloud Administration Command |
Execution | theoretical | moderate | T3 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (3 sources)
| ||||
| T1657 Financial Theft |
Impact | theoretical | weak | T4 |
↳ Evidence (1 source)
Financial theft is an outcome; access to decoy billing data is collection. | ||||
| T1098 Account Manipulation |
Persistence | confirmed | strong | T3 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (3 sources)
| ||||
| T1098.003 Additional Cloud Roles |
Persistence | theoretical | moderate | T3 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (2 sources)
| ||||
| T1098 Account Manipulation |
Privilege Escalation | confirmed | strong | T3 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (3 sources)
| ||||
| T1484 Domain or Tenant Policy Modification |
Privilege Escalation | theoretical | moderate | T4 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (2 sources)
| ||||
Evidence
- Decoy Object (D3-DO) — MITRE D3FEND standard
- Decoy Public Release (D3-DPR) — MITRE D3FEND standard
- MITRE Engage — adversary engagement matrix and ATT&CK mapping — MITRE 2022 standard
- MITRE ATT&CK Enterprise v20.0 — MITRE 2026 standard
- Baiting Inside Attackers Using Decoy Documents — Bowen, B.; Hershkop, S.; Keromytis, A.; Stolfo, S., SecureComm 2009 peer-reviewed