46 minutes ago · 22 min read4389 words · Tech · hide

If you haven't read Part 1, check it out first, as this is a continuation and picks up more details feeding into fixing up SSH and my VPS lockdown as a three part series.Part 1 closed the SSH port and moved everything behind Cloudflare Tunnel, so this part picks up the web side: locking the origin so only my Cloudflare zone can reach it, adding detection so I'd actually know if something went wrong, and sandboxing the services that sit behind it.In this part I'm going to cover:Locking the web origin so only my own Cloudflare zone can reach itDetection and recovery: auditd, alerts, off-site backups, a cloud firewall and patchingSandboxing the services with systemdFail2ban that actually works behind CloudflareHardening the analytics containerOnly my Cloudflare zone gets through: a direct hit stops at the firewall, someone else's zone stops at nginxStep 4: Lock the Web Origin to Your Cloudflare ZoneAllowing only Cloudflare's IP ranges proves traffic came through Cloudflare, but not whose…

Commenting on Bubbles has been removed. Why? If you want to talk about this post, write to the author, use the comments on their blog if it has them, or reply with a "RE:" post on your own blog. Suggestions? feedback@bubbles.town