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
[–] 2 points 21 hours ago

Wouldn't docker do the same with firewalld?

It acknowledges that it exists and just still uses it's own rules. You'd still have to configure it, configuration is just less stupid than ufw with docker.

My question is, who thought this was acceptable behavior at docker?

  • source
  • parent