48 minutes ago · 18 min read3535 words · Tech · hide

If you haven't read Parts 1 and 2, check them out first, as this is the last of the three and carries straight on from them.Part 1 closed the SSH port and Part 2 locked the origin and added detection. This part covers the remaining hardening: outside verification, further SSH tightening, the mistakes I made, and OS-level work that matters on the same box.In this final part I'm going to cover:Checking it all from the outsideGoing further with SSH: short-lived certificates, hardware keys and tighter settingsLocking down the Cloudflare account that everything now depends onThe mistakes that bit me along the wayKernel and OS hardening, plus housekeepingRe-checking it all against a critical nginx CVE, then moving to nginx.org's packagesWhat all of this doesn't protect againstStep 6: Check It From the Outside"Done" meant a scan of the origin IP finds nothing, so scan it from a machine that isn't the server, on a network that isn't Cloudflare's. Scanning your own server is normally fine, but…

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