This sheet is past its review date. Deadlines or advice may have changed since 5 Nov 2026.
Canaries and honeytokens: would you know an intruder is already inside?
This month, plant decoys on the paths intruders take first, such as a Kerberoastable honeytoken account, a fake password file on a share and fake cloud keys on admin and developer machines, and route every trip to whoever handles high-severity alerts at night. Treat each trip as an intrusion until you can name the person or tool that caused it.
If you only do five things
Send every trip to someone who acts at night.
Route them like the logging sheet's alerts, to a named owner and deputy. Ask your MDR provider in writing whether it acts on them: Microsoft's Defender Experts covers only High and Medium incidents, not custom detections3.
Build on tools you already run.
Defender for Identity, Windows auditing, CloudTrail and Microsoft 365 alert policies keep alert data in systems you control. Decoys work: in a test with over 130 red teamers, everyone facing decoy hosts set one off before reporting a successful exploit4.
Keep a register and tell almost no one.
Record each decoy's location, trigger and alert path for the few admins who need it, so nobody uses or deletes one by mistake. In the NCSC's trials, 90% of participants said they wouldn't publicly announce using deception6.
Plant your first decoys
A honeytoken account in Active Directory.
Create an unused user with an attractive name, an SPN, a long random password and no rights. Tag it Honeytoken in Defender for Identity (Microsoft 365 E5, E5 Security, EMS E5 or standalone7) to alert on its sign-ins, LDAP lookups and changes8. Either way, alert on event 4769 for the account, which needs Audit Kerberos Service Ticket Operations on domain controllers9.
A password file on a share.
List the honeytoken in it and audit reads with Audit File System and a SACL: Windows then logs event 4663 with the account and process10. In SharePoint, alert on Accessed file for its URL5;
app@sharepointhits are often retention policies11.Fake cloud keys.
Create an IAM user without permissions in a separate AWS account; leave its keys on admin and developer machines and in CI. With an active multi-Region trail, set an EventBridge rule in each Region to
ENABLED_WITH_ALL_CLOUDTRAIL_MANAGEMENT_EVENTS, or it misses read-only calls12.A decoy secret and a decoy cloud user.
With Key Vault logging on, alert on any
SecretGetfor a fake secret13 and on any sign-in by a decoy Entra ID user, the way Microsoft shows for emergency access accounts14.Names only a thief would use.
Put a canary hostname in SSH configs, RDP files and runbooks and a unique email address in fake customer and HR records, and alert on lookups and on mail your systems didn't send.
Free, self-hosted or paid
- canarytokens.org is free, with only an acceptable use policy. Thinkst runs it as a public service for any lawful purpose, promises only to work hard to keep it running and uses third parties such as Mailgun and AWS15. Use it to try token types, not for production.
- Self-host the open-source server. Its GPLv3-based license allows internal use; embedding it in proprietary software needs a commercial license17. Patch it like any internet-facing server.
- Decoy hosts. OpenCanary, BSD-licensed, emulates network services on a small VM; Thinkst Canary is its commercial version18. Ask vendors for a data processing agreement.
Germany: works council and data protection
- Involve the works council first. It co-determines technical systems designed to monitor employees' behavior or performance, and the Federal Labor Court counts any system objectively suitable for that, whatever the employer intends19. A decoy that logs which account opened it qualifies.
- Put the rules in a works agreement. Cover what is logged, who sees alerts, retention and that trips aren't used to judge performance.
- Mark placements as confidential. Works council members may not disclose business secrets the employer expressly marks as confidential20.
- Ask your data protection officer about external services. Alerts can identify staff, and the GDPR requires a contract with any processor16.
When a canary fires
Who or what touched it?
Check the account, host, IP address and process against the register of backups, scanners and tests.
Treat an unexplained trip as an intrusion.
Follow the incident response sheet: isolate without wiping and export the logs. Leave the decoy in place, or the attacker learns they were seen.
Reset what was within reach.
Reset the account that tripped it and every credential near the decoy, in one coordinated round if admin rights are at risk. If a canary key was used, treat its machine as compromised.
Record the cause.
If your own tool tripped it, move the decoy instead of excluding the tool.
Mistakes that cost the most
- A decoy that unlocks something real. A honeytoken with a weak password or real rights becomes a way in. Use a long random password, no extra groups and a Conditional Access block on Entra ID sign-in.
- Canary keys in public repositories. GitHub reports partner secrets found in public repositories to the provider, which may revoke them or contact you21. Keep keys where only an intruder looks.
- Trusting the Windows folder token. Thinkst says it doesn't work on Windows 1122. Audit the folder with a SACL instead.
- Alerts nobody reads. Defender for Identity rates honeytoken LDAP lookups as Low8, so a High-and-Medium email rule misses them. Make sure they reach someone.
What changed in 2026
- The UK tested deception at scale. In December 2025 the NCSC reported on an experiment with 121 organizations: most saw potential value in detecting novel threats, but misconfigured tools can miss threats, give false confidence or create openings for attackers6.
- Defender for Identity got easier to switch on. Since October 2026, its v3.x sensor runs on domain controllers without Defender for Endpoint, and turns on by itself where Defender for Endpoint runs, unless you opt out23.
- Sign-in page canaries are ending. Thinkst's Entra ID token, which flags proxied sign-in pages, needs custom CSS branding24. Tenants without it can't add it after 21 July 2026, and Microsoft will retire it25.
What you can skip
- Internet-facing honeypots. They tell you about the internet's scanners, not about your network. Put decoys inside.
- Fake environments that engage intruders. Decoy accounts, files and keys are enough to detect an intrusion.
- Hundreds of decoys before five work. Deception needs tuning as networks change6. Grow only as fast as you test.
- A deception platform before an on-call rotation. If nobody answers a High alert at night, a canary alert waits too (see the SOC and MDR sheet).
What this looks like at your size
Small team, no security staff
- Put a fake password file in SharePoint with an alert policy on Accessed file5; check that your plan allows custom alert policies.
- Leave fake cloud keys on the admin laptop if you use AWS.
- Send alerts to two people's phones and trip every decoy each quarter.
Growing, with IT or security staff
- Alert on event 4662 for AD canary objects that nobody may read1; audit tools trip them too.
- Self-host Canarytokens, or buy a product with a data processing agreement.
- Agree canary handling with your MDR provider and works council.
Enterprise or regulated
- Place decoys in each tier and network zone, including management, OT and cloud accounts.
- Report trips and time to response with your detection metrics.
- Include decoys in red team scopes and move any that testers walk past.