Skip to content

Configuration file

The manager's settings live in /opt/redpot/manager/rpot.json. The installer writes it; most settings never need to be touched.

rpot.json is secret

It holds the admin token, the bait seed and the plaintext baits. It is readable by root only. Do not copy it to tickets or chat.

After editing rpot.json, check that it kept its owner and mode, then restart the manager:

sudo ls -ln /opt/redpot/manager/rpot.json     # owner and mode must be the same as before the edit
sudo systemctl restart redpot

The console container runs as uid 10001 and must be able to read the file. Keep it valid JSON.

Settings you may change

Key Default Meaning
alerts.min_level 3 lowest incident level written to alerts.json. 4 records only compromises and honeytokens
logs.alerts true write logs/alerts.json
logs.events false also write every event to logs/events.json
logs.max_mb 50 rotate a log file at this size (it also rotates daily)
logs.keep 90 number of rotated .json.gz archives to keep (newest first)
console.retention_days 90 days the database keeps events and alert records
console.wall_days 7 how long a wall screen session lasts (1 to 90 days)
console.wall_allow empty networks allowed to use the wall link (set it with reset-token --wall-allow)
console.trust_xff false honour X-Forwarded-For for bait-document beacons behind your reverse proxy
console.trusted_proxies empty proxies whose X-Forwarded-For is used; empty = never, even with trust_xff
allowlist empty scanner allow-list (CIDRs)
internal_nets 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16 networks treated as internal
site not set location of the protected site on the world map; set it with rpotctl site

Example

"alerts": {"min_level": 3},
"logs": {"alerts": true, "events": false, "max_mb": 50, "keep": 90},
"console": {"retention_days": 90, "wall_days": 7},
"allowlist": ["10.0.5.20/32"]

Allow-list and internal networks

  • allowlist: sources that are expected to touch the decoys, such as your vulnerability scanner or IT admin hosts. Their events are recorded but never raise incidents.
  • internal_nets: private, CGNAT and link-local addresses are always internal. Add your own public ranges here so that they are treated as internal sources (internal map) instead of internet sources (world map).

Reverse proxy for bait-document beacons

If the console sits behind your own reverse proxy, the beacon from a bait document arrives from the proxy's address. To record the real client:

"console": {"trust_xff": true, "trusted_proxies": ["10.0.5.20/32"]}

X-Forwarded-For is used only for requests whose TCP peer is in trusted_proxies, and only its rightmost entry (the one your proxy adds). A source taken from it is never matched against the allow-list, so it cannot mute a bait alert. The installer never sets this.

Data retention

The console database keeps events and alert records for console.retention_days (default 90). The purge runs every 6 hours and removes events and alert records only; incident rows are not purged. The log files alerts.json and events.json have their own rotation (logs.keep).

Enterprise feature: available in ReD-Pot Enterprise

Configurable retention per data type. Enterprise sets retention separately for events, alert records, incidents, alert deliveries and the audit log, from the console settings.

About ReD-Pot Enterprise · Compare editions · Contact us for a licence

Settings that are fixed

The persona (domain, industry, users) and the bait set are fixed after the install. See Persona, baits and honeytokens.