Case C60AE1 · Blue team / DFIR · L2 Practitioner

Honeytokens and Canaries

Practise as: Explain itLevel: L2 Practitioner
  1. 01 What is it?
  2. 02 How is it abused?
  3. 03 How do you stop it?
What a strong answer covers

Try it out loud first. Then check yourself:

  1. Decoys with no legitimate use: fake AWS keys, AD accounts, file shares, DNS or URL tokens; any touch is a high-fidelity alert.
  2. Example: a honey account with an SPN; any 4769 ticket request for it signals Kerberoasting with near-zero false positives.
  3. Attackers fingerprint decoys: never-used accounts, odd creation dates, keys tied to known canary services. Make them believable.
  4. Place them where attackers look: credential files on admin hosts, LSASS-adjacent creds, code repos, password managers.
  5. 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?

Go deeper

More Blue team / DFIR cards

All Blue team / DFIR cards →

cardosec draws a security topic and gives you a clock: explain it out loud with no notes, then see what you covered and what you missed. Free during early access.

Reviewed 2026-10-09