EPOCH SECURITY

Epoch Security

Documentation

A quick guide for server administrators. Technical details are in the project README.

Setup

  • Add the bot via “Invite bot” and confirm the requested permissions.
  • Move the bot role as high as possible in your server settings – Discord only allows it to act against members below its highest role.
  • Run /setup log-channel:#security or set the log channel in the dashboard.
  • Review limits and countermeasures under “Anti-Nuke”. New servers run in dry-run mode.

Dry run

In dry run, Epoch Security detects and logs incidents but only simulates punitive actions (timeout, remove roles, kick, ban, lockdown). Watch the logs for a few days before you disable dry run.

Limits of detection

  • Attributing an actor relies on the Discord audit log, which is delayed and not always complete.
  • Without a reliable attribution nobody is punished – you only get an alert.
  • The bot cannot act against the server owner or members with an equal or higher role.
  • The bot cannot prevent actions beforehand; it detects and limits the damage.
  • Phishing lists are never complete. New domains are only caught by heuristics and your blocklist.
  • During a Discord or bot outage there is no protection. Keep permissions granted to third parties minimal.

Dashboard permissions

  • Manage Server or Administrator: configuration, logs, lockdown.
  • Administrator: whitelist/trust, disabling dry run, kick/ban as a countermeasure, backup restore.