Security - serious question (not trolling)

Configuration
12

Assuming you’ve worked through this, then there’s only a few other easy things to do:

  1. Use a reverse proxy server for SSL. Using a proxy server allows you to do filtering there, rewrite requests, limit access, and more. You can take this up another level by using one with WAF (web application firewall) capabilities.
  2. Don’t use port 443 or 8123, or another common port. No, this isn’t security, but if you pick a random high numbered port it cuts down on the number of people that will find it. It’s hard to pick a lock you can’t find.
  3. Deploy the likes of fail2ban on your proxy server
  4. Consider only permitting remote access to the bits you need - I use my proxy server to only allow remote access to webhooks. If I want remote access to the UI I’ll just use my VPN, which brings me to…
  5. Use a VPN for remote access to the UI
  6. Keep an eye on the proxy logs for signs anybody has found your server and is attempting to compromise it
4 Likes