D010F1
Credential
🎫 Honey Session Token
Planted fake STS/OAuth session tokens.
What it is
Short-lived cloud session credentials or OAuth tokens, issued by an identity that grants nothing and planted where tooling caches them. Attackers prize live sessions because they skip the login step entirely. Any call made with the planted token is logged under that session, but the token expires, so it must be re-issued to stay useful as a lure.
Implementation requirements
- AWS: from a decoy IAM user or role with no permissions, issue temporary credentials (
aws sts get-session-token, valid 15 minutes to 36 hours, oraws sts assume-role). Plant them where tooling caches them, such as anaws_session_tokenentry in~/.aws/credentials - Temporary credentials expire, and an expired token gives you no reliable signal. Automate re-issuing so a fresh token is always in place
- Monitoring: CloudTrail events whose access key ID is the planted temporary key (it starts with
ASIA), or whose principal is the decoy user or role - OAuth and SaaS: plant a token only for a decoy account that holds nothing. Alert on any sign-in or token use by that account in Entra sign-in logs or Google Workspace login and OAuth logs. Those logs arrive minutes to hours late
- Safety: the issuing identity grants nothing, so the token grants nothing. OPSEC: session names and expiry times like those your real tooling produces
- Rollback: Stop the re-issuing job, then delete the decoy user or role. Remove planted token files.
- Upkeep: The re-issuing job is the upkeep: alert if it fails, because an expired token is a dead lure. Weekly proof-of-life use of the current token.
Technologies
AWSAzure
ATT&CK coverage 10
| Technique | Tactic | Status | Confidence | Tier |
|---|---|---|---|---|
| T1528 Steal Application Access Token |
Credential Access | theoretical | moderate | T4 |
| ↳ Detection point: the decoy fires at a later step of the attack | ||||
↳ Evidence (3 sources)
A stolen honey token fires when it is used, not when it is stolen. | ||||
| T1078 Valid Accounts |
Initial Access | confirmed | strong | T2 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (5 sources)
| ||||
| T1078.004 Cloud Accounts |
Initial Access | confirmed | strong | T4 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (4 sources)
| ||||
| T1021.007 Cloud Services |
Lateral Movement | confirmed | strong | T2 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (3 sources)
| ||||
| T1550 Use Alternate Authentication Material |
Lateral Movement | confirmed | strong | T2 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (4 sources)
| ||||
| T1550.001 Application Access Token |
Lateral Movement | confirmed | strong | T2 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (3 sources)
| ||||
| T1550.004 Web Session Cookie |
Lateral Movement | confirmed | strong | T2 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (2 sources)
| ||||
| T1548.005 Temporary Elevated Cloud Access |
Privilege Escalation | theoretical | moderate | T3 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (2 sources)
Assuming a decoy role is closer to T1078.004; the T1548.005 fit is partial. | ||||
| T1078 Valid Accounts |
Stealth | confirmed | strong | T2 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (5 sources)
| ||||
| T1134 Access Token Manipulation |
Stealth | theoretical | moderate | T2 |
| ↳ Detection point: the decoy fires at a later step of the attack | ||||
↳ Evidence (2 sources)
| ||||
Evidence
- Decoy User Credential (D3-DUC) — MITRE D3FEND standard
- Decoy Session Token (D3-DST) — MITRE D3FEND standard
- MITRE Engage — adversary engagement matrix and ATT&CK mapping — MITRE 2022 standard
- MITRE ATT&CK Enterprise v20.0 — MITRE 2026 standard
- Browser Honeytoken Detection for Infostealers — Hookset 2026 industry