Honeypot Canaries
A honeypot canary is a fake file that appears as sensitive resource (AWS-credentials, SSH-key, .env). No legitimate process ever reads it. As soon as something opens it → critical alert.
What the agent places
Default on Linux:
/root/.aws/credentials-backup/root/.ssh/id_rsa.monsys-backup/etc/monsys/.canary/tmp/passwords-backup.txtOn Windows:
C:\ProgramData\monsys\canary.txtC:\ProgramData\aws\credentials.bakC:\Windows\Temp\admin-creds.txtThe content appears as real credentials but contains clearly fictional values (AKIAIOSFODNN7EXAMPLE). Whoever uses them will not gain access.
Detection
- Linux — inotify watch on every canary. Read/write/delete event triggers a
honeypot_eventpayload to the hub. - Windows —
ReadDirectoryChangesW.
What to do when triggered
- Identify the
process_nameandprocess_pidin the alert. - Check the full process via
Inventory → Processeson the server detail page. - Consider
KillProcessorIsolateNetworkvia Emergency Actions. - Make a memory dump (
MemoryDump) before stopping the process — IOC’s remain preserved.
Note: I’ve kept all line breaks, paragraph structure, and markdown formatting exactly as in the original document.