Decoys¶
A decoy is one fake server in its own container. Community Edition runs up to 3 decoys in total, counting local decoys on the manager, remote sensors, and pending join commands. See Decoy roles for what each role emulates.
The decoy limit¶
| Counts toward the limit | Frees its slot when |
|---|---|
| a local decoy on the manager | you run sudo ./install.sh remove-decoy NAME (revoking it in the console does not free the slot) |
| a remote sensor | you revoke it in Deception |
| a pending join command | you cancel it in Deception, or it expires after 24 hours unused |
The Deception tab shows "n of 3 decoys". When all slots are used, Add a sensor is disabled and explains why, and
a full manager answers a valid join with "decoy limit reached". The limit is enforced locally by the installer,
rpotctl, enrollment, the database and the sensor API. There is no licence server and nothing phones home.
Enterprise feature: available in ReD-Pot Enterprise
More than 3 decoys. In Enterprise the number of decoys is set by a signed licence file, not fixed at 3.
About ReD-Pot Enterprise · Compare editions · Contact us for a licence
Add a decoy later¶
Typical case: the server started with one network card, carrying the manager and one decoy. Later it gets a second NIC that should host a second decoy on that NIC's own address.
Do not reinstall
A new install generates a new persona, new baits and a new certificate. Every bait already planted or stolen stops
being recognised, and remote sensors must join again. Use add-decoy instead.
sudo ./install.sh add-decoy # interactive
sudo ./install.sh add-decoy --yes --decoy-if eth1 --roles windows-domain-controller --names RS-DC-02 # unattended
sudo ./install.sh add-decoy --dry-run # show everything, change nothing
add-decoy:
- finds the install in
/opt/redpot/manager(or--dir) and checks the decoy count with the running manager. If all 3 slots are used it stops; if the manager is not running it asks you to start it (sudo systemctl start redpot); - offers only interfaces without a decoy (the management interface counts as free while no decoy is on it), and asks for the role and the host name;
- runs the same checks as a fresh install: other services on the address (offered to stop, re-enabled by uninstall),
the DHCP warning, and host SSH:
- new decoy on another interface: host SSH listens only on the management IP;
- new decoy on the management interface and SSH not moved yet: host SSH moves to a random port, the allow-lists are asked again if they are still open to everyone, and host services that would become unreachable on that interface are listed for confirmation;
- adds the decoy. Existing decoys keep their keys, containers and persona; baits are planned for the new decoy set and every existing honeytoken stays valid;
- updates
firewall.sh,INSTALL-INFO.txtand the login banner, reloads the service and runs the self-test.
Remove a decoy¶
This removes the container, its data volume, and its firewall and TTL rules, and frees the slot. The SSH address pin is
lifted when no decoy sits on another interface any more. uninstall restores everything, including changes made by
add-decoy.
Decoy health¶
Every 30 seconds each decoy checks its listeners. A dead or unbound listener is restarted and reported, and the manager opens an L4 "service down - possible DoS" incident for that decoy; the console marks the service in red. A decoy that stops reporting for more than 2 minutes opens an L4 "stopped reporting - possible tampering" incident.