D009F2
Credential
🎫 Honey Certificate
Decoy TLS/auth certificates in key stores.
What it is
A decoy certificate in a key store, or a certificate credential on an app registration that has no role assignments. Certificates authenticate services and are rarely watched, which makes them attractive to steal. Reading the certificate is logged by the key store, and signing in with it is logged as a service principal sign-in.
Implementation requirements
- Azure: a certificate credential on an app registration with no role assignments. Any sign-in with it appears in the service principal sign-in logs. Thinkst Canarytokens offers this as its Azure Login Certificate token
- Key stores: a certificate in Key Vault, ACM or Certificate Manager with an attractive subject name. Key Vault records
CertificateGetand, for the private key,SecretGetin itsAuditEventlog - If the certificate is meant to be presented in TLS, it needs a valid chain for a decoy host name you control, and the handshake log on that host is the signal
- Safety: the certificate authenticates nothing real, and its private key exists nowhere else
- OPSEC: issuer, validity period and key size like your real certificates
- Rollback: Remove the certificate credential from the app registration and delete the certificate from the key store. Revoke it if it was issued by a CA.
- Upkeep: Renew before expiry, matching real certificate lifetimes. Quarterly proof-of-life sign-in or read.
Technologies
AzureAWSGCP
ATT&CK coverage 4
| Technique | Tactic | Status | Confidence | Tier |
|---|---|---|---|---|
| T1606.002 SAML Tokens |
Credential Access | theoretical | weak | T4 |
| ↳ Detection point: the decoy fires at a later step of the attack | ||||
↳ Evidence (1 source)
No source covers decoy SAML signing certificates. | ||||
| T1649 Steal or Forge Authentication Certificates |
Credential Access | confirmed | strong | T4 |
| ↳ Detection point: the decoy fires at a later step of the attack | ||||
↳ 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)
| ||||
| T1098.001 Additional Cloud Credentials |
Persistence | theoretical | moderate | T4 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (3 sources)
| ||||
Evidence
- Decoy User Credential (D3-DUC) — MITRE D3FEND standard
- MITRE Engage — adversary engagement matrix and ATT&CK mapping — MITRE 2022 standard
- MITRE ATT&CK Enterprise v20.0 — MITRE 2026 standard
- Canarytokens token guides (MS Word, Windows Directory, Network Folder, Kubeconfig, AWS Infrastructure, DNS, Azure Login Certificate, MySQL Dump) — Thinkst Applied Research industry