Skip to content

Breadcrumb chain

Baits point at other decoys, so an intruder who takes the bait walks deeper into the trap and leaves a trail.

  • The chain is planned from the decoys that are really deployed, local and remote. Every crumb names only those hosts, by their real names and FQDNs.
  • Every decoy holds a credential for each other decoy, plus one that works on itself, so even one or two decoys give a complete path.
  • Each token's planted field, and so the incident text, names the decoy and path where the bait really lives.

Example with all roles

<web>, <bkp> and <dns> stand for the real names of those decoys.

FS   \IT\passwords.txt ----------> WEB  ssh deploy / ...           -> L5
     \IT\keys\<web>_deploy.key --> WEB  ssh (public key)            -> L5
     \IT\passwords.txt ----------> BKP  ftp backup, DNS ssh dnsadmin, svc_scan (DC LDAP / FS SMB)
WEB  /.env ----------------------> WEB  /admin (seed password), BKP ftp (DB password reuse), DC LDAP (svc_web)
BKP  <web>_portal_db_*.sql ------> WEB  /admin portal (MD5 + hint)
BKP  configs/backup_job.ps1 -----> DC LDAP / FS SMB (svc_backup); pull_<web>.sh -> WEB ssh; upload.netrc -> itself
DC   SYSVOL Groups.xml cpassword > local admin on FS / LDAP bind
DC   NETLOGON logon.bat, ftp_<bkp>.txt, deploy_<web>.cmd, dns_reload_<dns>.cmd -> LDAP, BKP ftp, WEB ssh, DNS ssh
DC   LDAP svc_sql (SPN) ---------> Kerberoasting TGS-REQ
DNS  ~dnsadmin notes / nsupdate / .smbcredentials -> WEB, BKP, DC, FS, itself
FS   *.docx opened in Word ------> beacon to the manager            -> L5 (who opened it, from where)

Community Edition runs up to three of these roles at once; the chain covers the ones you deploy.

Adding decoys keeps the chain valid

Token ids, passwords and SSH keys are derived from a manager-only bait_seed, the persona and the host names. Adding a decoy keeps every existing token (stolen baits stay valid, the set of decoys they work on only grows) and adds crumbs for the new one. Remote enrollment uses the same planner; its new tokens are stored on the manager.

In the console

The console draws the chain as an attack path for each source, for example RS-FS-01 → RS-WEB-01 → RS-BKP-01 → bait document, with timestamps. Open the source on the Hosts tab or click it on the internal network map.