Persona, baits and honeytokens¶
Persona¶
The persona is the company the decoys pretend to belong to. You give two answers at install time:
| Input | Example | Derived from it |
|---|---|---|
AD/DNS domain (--domain) |
corp.ararat-bank.am |
company name "Ararat Bank", NetBIOS name ARARATBANK, mail domain ararat-bank.am |
industry (--profile) |
bank, hotel, government, it, generic |
file names and contents that fit the industry |
- The NetBIOS name is the first domain label without hyphens. When that is longer than 15 characters, its first word is
used (
northwind-traders-intl.combecomesNORTHWIND). - 14 users are picked from a built-in pool of first and last names with a random per-install seed. The seed also picks
the username format (
a.petrosyan,anna.petrosyan,apetrosyan,anna_p). - There is no default domain: the same default on every install would be a fingerprint. Internationalised (
xn--) domain labels are refused. - The identity is used in banners, TLS certificates, SMB server names, user lists, file names and passwords.
The persona is fixed for the life of an install. Changing it means a new install (with new baits and new join strings for remote sensors).
To see the persona and the planted baits in plaintext on the manager:
The installer tags the image rpot:<version>, whether it was downloaded or built locally.
Enterprise feature: available in ReD-Pot Enterprise
Editable persona and users. Change the company name, NetBIOS name, mail domain, username format, users and departments after the install, without reinstalling.
About ReD-Pot Enterprise · Compare editions · Contact us for a licence
Baits¶
Each role carries a fixed set of baits. The set and the structure of the files cannot be edited, uploaded or replaced in Community Edition, but every installation gets different passwords, keys, users, dates and file contents.
| Role | Baits |
|---|---|
| Windows file server | IT\passwords.txt, IT\keys\*_deploy.key (SSH key), departmental shares, Salaries_2026.docx and Network_Overview.docx that report when opened in Word |
| Linux web hosting | /.env with the portal admin seed password, a database password reused on the backup FTP and (with a DC) an LDAP bind account; robots.txt; SSH home directories |
| FTP / backup server | database dump with an admin MD5 hash and hint, a site archive, configs/backup_job.ps1 (domain service account), scripts and upload.netrc with passwords for the other decoys |
| Windows domain controller | SYSVOL\...\Groups.xml with a GPP cpassword; NETLOGON\logon.bat and scripts with passwords; LDAP honey users including the Kerberoastable svc_sql |
| Linux DNS server | a zone that resolves the other decoys; the dnsadmin SSH password planted on other decoys; notes with credentials in ~dnsadmin |
Bait files are dated per file at office-hours times, and .docx baits carry Word-like metadata (author and editor from
the staff list). Details per role: Decoy roles. How the baits link the decoys together:
Breadcrumb chain.
Honeytokens¶
Every bait is a honeytoken with a unique id. Token ids, passwords and SSH keys are derived from a manager-only
bait_seed in rpot.json, the persona and the host names. When a decoy is added, every existing token is kept (stolen
baits stay valid) and crumbs for the new decoy are added. Remote sensors only receive a hashed honeytoken index, never
plaintext bait passwords.
See Honeytokens for what happens when one is used.