D020F1
Data
🗄️ Honey Secret
Fake entries in Secrets Manager/Key Vault.
What it is
A secret in a secrets manager whose value is itself a honeytoken, such as a credential for an identity that grants nothing. Secret stores are among the first places attackers look once they hold a cloud identity. Reading the decoy secret is logged per secret, even during bulk reads, and using the credential inside it alerts again.
Implementation requirements
- AWS: a Secrets Manager secret with an attractive name. Azure: a Key Vault secret. GCP: a Secret Manager secret. Its value is itself a honeytoken (D006) or a credential for a decoy service
- Monitoring: AWS logs
GetSecretValuein CloudTrail for both single and batch (BatchGetSecretValue) retrieval, so bulk reads still name the decoy. Azure:SecretGetin the Key VaultAuditEventlog via a diagnostic setting. GCP:AccessSecretVersionis a Data Access log; enable DATA_READ for Secret Manager - Listing secrets (
ListSecrets,SecretList) returns every name and does not single out the decoy - Safety: the secret and the credential inside it grant nothing. OPSEC: rotation settings, tags and description like real secrets
- Rollback: Delete the secret (schedule deletion where recovery windows apply). Revoke the credential inside it.
- Upkeep: Rotate it like real secrets. Monthly proof-of-life read.
Technologies
AWSAzureGCP
ATT&CK coverage 4
| Technique | Tactic | Status | Confidence | Tier |
|---|---|---|---|---|
| T1213 Data from Information Repositories |
Collection | confirmed | strong | T2 |
| ↳ Detection point: the decoy fires at a later step of the attack | ||||
↳ Evidence (5 sources)
| ||||
| T1552 Unsecured Credentials |
Credential Access | confirmed | strong | T2 |
| ↳ Detection point: the decoy fires at a later step of the attack | ||||
↳ Evidence (4 sources)
| ||||
| T1555 Credentials from Password Stores |
Credential Access | confirmed | strong | T4 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (6 sources)
| ||||
| T1555.006 Cloud Secrets Management Stores |
Credential Access | confirmed | strong | T4 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (3 sources)
| ||||
Evidence
- Decoy Object (D3-DO) — MITRE D3FEND standard
- MITRE Engage — adversary engagement matrix and ATT&CK mapping — MITRE 2022 standard
- Tracebit for AWS — canary resources and credentials — Tracebit industry
- Deploy and monitor Azure Key Vault honeytokens with Microsoft Sentinel — Microsoft industry
- Canarytokens token guides (MS Word, Windows Directory, Network Folder, Kubeconfig, AWS Infrastructure, DNS, Azure Login Certificate, MySQL Dump) — Thinkst Applied Research industry
- MITRE ATT&CK Enterprise v20.0 — MITRE 2026 standard