🔑 Honey Cloud Group
Decoy permission groups (e.g., "prod-admin-group").
What it is
A decoy permission group with a name implying privileged access, discoverable by anyone enumerating groups in the directory. It catches two distinct behaviours: reconnaissance, when an attacker lists groups looking for a privilege path, and persistence, when an attacker adds a principal they control to a group that sounds powerful. The group grants nothing, so the addition gives them no access while giving you a confirmed signal.
Implementation requirements
- AWS: IAM group with an attractive name and an attached policy that grants nothing, or explicitly denies
- Azure: Entra ID security group with no role assignments and no application ownership
- GCP: Google Group in the organisation with no IAM bindings on real projects
- Keep it empty, or seed it only with the decoy identities from D002 and D003 so the membership looks plausible under inspection
- Monitoring: CloudTrail
AddUserToGroup,ListGroupsForUserandGetGroup; Entra ID group-membership change audit events; GCP group audit logs - OPSEC: match your real group naming convention. A name like
prod-admin-grouponly works if your real groups look like that - Rollback: Delete the group, after confirming it has no members.
- Upkeep: Quarterly proof-of-life: a membership read and an add attempt from a test principal.
Cost
Negligible. Groups are free directory objects on all three providers. Cost is audit-log ingestion only.
Indicative only. Cloud pricing and licensing change — check the provider's official pricing pages for current rates before you budget.
Technologies
ATT&CK coverage 7
| Technique | Tactic | Status | Confidence | Tier |
|---|---|---|---|---|
| T1069 Permission Groups Discovery |
Discovery | confirmed | strong | T2 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (2 sources)
| ||||
| T1069.002 Domain Groups |
Discovery | confirmed | strong | T1 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (2 sources)
| ||||
| T1069.003 Cloud Groups |
Discovery | theoretical | moderate | T1 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (2 sources)
Listing groups does not name the decoy; reading the decoy group itself does. | ||||
| 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)
| ||||
| T1136 Create Account |
Persistence | theoretical | moderate | T4 |
| ↳ Detection point: the decoy fires at a later step of the attack | ||||
↳ Evidence (3 sources)
The honey credential fires on its first API call; inside a honey cloud account, account creation is seen in-decoy. | ||||
| T1098 Account Manipulation |
Privilege Escalation | confirmed | strong | T3 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (3 sources)
| ||||
Evidence
- Decoy User Credential (D3-DUC) — MITRE D3FEND standard
- Deceptive defense: best practices for identity-based honeytokens in Microsoft Defender for Identity — Microsoft 2023 industry
- Logging management events — AWS CloudTrail User Guide — Amazon Web Services industry
- MITRE Engage — adversary engagement matrix and ATT&CK mapping — MITRE 2022 standard
- MITRE ATT&CK Enterprise v20.0 — MITRE 2026 standard
Research basis: MITRE D3FEND D3-DUC, with Microsoft's 2024 identity-honeytoken guidance and the Azure-Sentinel HoneyTokens solution as the industry sources. The DOAR evidence audit rated this Moderate on the technique-evidence scale — industry-documented rather than independently studied.