Inspired by this comment to try to learn what I’m missing.

  • Cloudflare proxy
  • Reverse Proxy
  • Fail2ban
  • Docker containers on their own networks
  • catloaf@lemm.ee
    link
    fedilink
    English
    arrow-up
    13
    ·
    24 days ago

    I don’t put it on the Internet.

    I have automatic updates enabled and once in a while I scan with Nessus. Also I have backups. Stuff dying or me breaking it is a much greater risk than getting hacked.

    • woodsb02@lemmy.ml
      link
      fedilink
      English
      arrow-up
      9
      ·
      24 days ago

      I agree - I don’t expose anything to the internet other than the WireGuard endpoint.

      I’m only hosting services that my immediate family need to access, so I just set up WireGuard on their devices, and only expose the services on the LAN.

      I used to expose services to the internet, until one of my #saltstack clients was exploited through a very recent vulnerability I hadn’t yet patched (only a week or so since it was announced). I was fortunate that the exploit failed due to the server running FreeBSD, so the crontab entry to download the next mailicious payload failed because wget wasn’t available on the server.

      That’s when I realised - minimise the attack surface - if you’re not hosting services for anyone in the world to access, don’t expose them to everyone in the world to exploit.

      • rockstarmode@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        arrow-down
        1
        ·
        24 days ago

        I don’t expose anything to the internet other than the WireGuard endpoint.

        This is the way