![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://infosec.pub/api/v3/image_proxy?url=https%3A%2F%2Flemmy.world%2Fpictrs%2Fimage%2F8286e071-7449-4413-a084-1eb5242e2cf4.png)
- Turn off password login for SSH and only allow SSH keys
- Cloudflare tunnel
- Configure nginx to resolve the real IPs since it will now show a bunch of Cloudflare IPs. See discussion.
- Use Fail2ban or Crowdsec for additional security for anything that gets past Cloudflare and also monitor SSH logs.
- Only incoming port that needs to be open now is SSH. If your provider has a web UI console for your VPS you can also close the SSH port, but that’s a bit overkill.
You are correct. The provider owns the IP and also VPS. They theoretically have the ability to do anything within those confines. Same thing with your nameserver provider with your DNS records and the domain itself with the registrar. There’s a certain level of trust that needs to be accepted for anything that goes outside the confines of your house. The good thing is those companies have more to lose than you by breaking that level of trust.