Case C60AE1 · Blue team / DFIR · L2 Practitioner
Honeytokens and Canaries
- 01 What is it?
- 02 How is it abused?
- 03 How do you stop it?
What a strong answer covers
Try it out loud first. Then check yourself:
- Decoys with no legitimate use: fake AWS keys, AD accounts, file shares, DNS or URL tokens; any touch is a high-fidelity alert.
- Example: a honey account with an SPN; any 4769 ticket request for it signals Kerberoasting with near-zero false positives.
- Attackers fingerprint decoys: never-used accounts, odd creation dates, keys tied to known canary services. Make them believable.
- Place them where attackers look: credential files on admin hosts, LSASS-adjacent creds, code repos, password managers.
- Wire alerts straight into IR with an owner and playbook; a canary that fires into an unread mailbox is worthless.
If the interviewer pushes back
- How would you deploy honeytokens across 20,000 endpoints without confusing your own IT staff or breaking audits?