Access allow-lists¶
The manager has three admin ports. Each has its own allow-list of networks:
| Admin port | Who needs it | Option |
|---|---|---|
| Web UI (HTTPS, random port) | analysts and admins; bait Word documents report here too | --allow-ui |
| Sensor API (HTTPS, random port) | remote sensors | --allow-sensor |
| Host SSH | administrators | --allow-ssh |
The admin ports answer only on the management interface and only to their allow-lists. For everyone else they look
closed (TCP reset, like any closed port). 0.0.0.0/0 means anyone. Your current SSH client is always allowed, an IPv6
client too.
When a decoy shares the management interface, all three lists default to your own SSH client address (/32), and an
unattended install must pass --allow-ui, --allow-sensor and --allow-ssh explicitly. A list that is open to anyone or
contains the decoy's own LAN is warned about, because a port scan of the decoy would then show that admin port.
Bait documents use the web UI port
Bait Word documents call home to the web UI port. With a restricted web UI allow-list, a bait document opened on a host outside that list is not reported. Bait files, credentials and keys used against the decoys are not affected.
Networks must be written as networks: an entry with host bits set (10.1.2.3/8) is refused with the network and the
single-address form to type instead.
Change the lists later: set-access¶
set-access changes the lists of a manager install without reinstalling. Persona, baits and the admin token stay.
sudo ./install.sh set-access # asks for all three, current lists as defaults
sudo ./install.sh set-access --yes --allow-sensor 10.20.0.0/24 # only the named lists change
sudo ./install.sh set-access --yes --allow-ui 10.8.0.0/24 --allow-ssh 10.8.0.0/24
What it does:
- Applies the install's exposure checks. On an address a decoy shares, a list that is open to anyone or contains the
decoy's own LAN must be confirmed (default no). With
--yesit is refused unless you add--accept-exposure. - Warns when the new sensor-API list leaves out an enrolled remote sensor's address (that sensor would be refused and go offline); interactive runs ask to confirm.
- Rewrites
firewall.shand swaps the rules in without a gap: the old rules stay in effect until the new ones are complete. If the new rules fail, the previous rules and the previousfirewall.shstay, andinstaller.jsonis unchanged. - Your current SSH client always stays allowed.
- Web UI and sensor API connections already open from removed addresses are cut if the
conntracktool is installed; otherwise they stay open until they close (sudo systemctl restart redpotends them). - Host SSH sessions are never cut automatically, so your own session is safe. The output shows how to list and end them.
- Unchanged lists change nothing.
Wall screens¶
The read-only wall link has its own optional screen allow-list, set with reset-token --wall-allow. See
SOC wall screen.
Known scanners¶
To stop your own vulnerability scanner or IT admin hosts from raising incidents, add them to the scanner allow-list
(allowlist in rpot.json). Their events are recorded but never raise incidents. See
Configuration file.
Enterprise feature: available in ReD-Pot Enterprise
Block an attacker IP on all decoys. From an incident, a host or a blocklist tab, one action blocks a source address or network on every decoy and remote sensor, with a reason and an expiry.
About ReD-Pot Enterprise · Compare editions · Contact us for a licence