Remote sensors¶
A remote sensor is one decoy on another server (another VLAN, a branch office, a cloud VPC) that reports to your manager. It counts toward the 3-decoy limit from the moment its join command is created.
Add a sensor¶
- On the manager console: Deception → Add a sensor (another server). Enter a host name and a role (the IP is optional; the sensor's installer reports it). You get the command and, in its own copy box, a one-time join string, valid for 24 hours.
-
On the new server: clone the repository and run the sensor installer, then paste the join string when asked:
-
The installer checks that the manager is reachable and that its certificate fingerprint matches the join string. A different certificate (wrong server or man-in-the-middle) is refused before anything is installed.
- It asks two questions, which may have the same answer:
- Which interface reaches the manager? (pre-selected from the routing table)
- Which interface should the decoy live on?
- The service is
redpot-sensor. The sensor appears in the manager within seconds.
The join string is a secret
It looks like redpot://10.10.0.5:62667/AbC...xYz#53C6EB7A... and can be redeemed once. Paste it when the installer
asks, or for unattended installs pass it on standard input or in a root-only file:
sudo ./install.sh sensor --yes --join - < join.txt
sudo ./install.sh sensor --yes --join-file /root/join.txt # chmod 600; delete it afterwards
Never put it on the command line (--join 'redpot://...'): other users of the server can read it with ps while
the installer runs, and redeem it first.
Where the decoy answers¶
There is no address question: the decoy answers on the IP of the interface you chose.
| Decoy interface | Host SSH |
|---|---|
| the interface that reaches the manager | moves to a random port. The installer asks who may use host SSH (default: your own SSH client; --allow-ssh is required with --yes). The decoy follows a DHCP change of that address |
| another interface | stays on 22 and listens only on the manager-link IP |
A sensor has no inbound admin ports, so one network card is enough. The same firewall policy as on the manager applies:
on the decoy interface only the decoy's ports answer. --no-ssh-move works only with the decoy on another interface.
Give the sensor a static address or a DHCP reservation
The manager's sensor-API allow-list names the sensor's address or network. The decoy follows a DHCP change on the
manager-link interface, but the manager's allow-list does not: after a new lease the manager refuses the sensor, the
decoy shows as offline (L4 "stopped reporting") and its events stay in the sensor's local undelivered log. The
sensor installer warns when the manager link is a DHCP lease. If the address did change, allow the new one on the
manager without reinstalling: sudo ./install.sh set-access --yes --allow-sensor 10.20.0.0/24. Allowing the
sensor's subnet instead of a single address avoids the problem.
Role and enrollment details¶
- The decoy's role is chosen on the manager and arrives with the enrollment. The join string may carry it as a hint
(
redpot://HOST:PORT/TOKEN?role=windows-file-server#FINGERPRINT) so the installer can show the role before anything changes. - If the install stops after enrollment (for example a port the decoy needs is in use), it keeps the enrollment: fix the cause and run the installer again. No new join string is needed.
- If the manager is full when the sensor enrolls, the installer stops with "enrollment refused: decoy limit reached" and nothing is installed.
Revoke, cancel, delete¶
| Action (Deception tab) | Effect |
|---|---|
| Revoke | the sensor's key stops working at once and its slot is free |
| Cancel (pending join) | the join string becomes invalid and its slot is free at once |
| Delete | removes a revoked sensor from the list; its events stay |
What the link costs¶
One encrypted heartbeat every 25 to 35 seconds over a single kept-alive TLS connection: about 0.6 kbit/s and 5 MB per day. A full attack (scan, logins, file theft) is about 11 KB.
If the manager is unreachable¶
The sensor retries the batch in flight for up to 60 seconds, so a manager restart loses nothing. After that, events are written only to a local log and are never sent later:
- remote sensor:
/opt/redpot/sensor/data/undelivered-<NAME>.jsonl - decoy on the manager:
undelivered-<NAME>.jsonlin the Docker volumeredpot_<name>-data
The file has mode 0600 and is capped at 50 MB (RPOT_UNDELIVERED_MAX_MB; the newest half is kept when it is full).
After 2 minutes of silence the manager opens an L4 "possible tampering" incident for that decoy. When the sensor
reconnects it sends one note with the number of undelivered events and the first and last timestamp (no event content),
shown on that decoy's incident.
Enterprise feature: available in ReD-Pot Enterprise
Offline spool and replay. Enterprise sensors buffer events on disk while the manager is unreachable and send them when the link is back.
About ReD-Pot Enterprise · Compare editions · Contact us for a licence
Residual risk on remote sensors
Add a switch or firewall ACL so that the decoy IP may only answer connections, never initiate them.