When you spin up a fresh public Linux instance, automated scanners start knocking on your doors within milliseconds.

It doesn't take much to get locked down properly, but missing a few basics can leave you exposed.

I've put together a straightforward guide covering the essential hardening steps from UFW and SSH key-only auth to secure Docker bindings and automated maintenance.


Original content by The Unknown Universe, written by a human and not AI generated!

you are viewing a single comment's thread
view the rest of the comments
[–] 14 points 2 days ago*

More Docker hardening*

Consider rootless docker or Podman. If that is not for you:

* Note that these tips are less "fire-and-forget, sane defaults" and can be much more finicky. Whether they work well depends on the service in question. They may break container deployments and are often a matter of trial and error until you get them just right. (Feel free to hit me up on details; if I happen to be running the same services as you are, I may be able to tell you what works and what doesn't.)

  • source