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!



A “secret” administrator account name is not a second authentication factor: it’s just another “something you know”, basically the same as using a slightly longer password.
On top of that, account names are generally not treated with the same confidentiality passwords or private keys are treated with: while you can trust that software and collaborators will not leak a password or private key, you cannot make the same assumption about usernames.
Yeah that was a bad choice of words on my part.
Consider though that everything I handle with a public facing ip gets 69 million attempts to login as “root”, “admin”, “docker” and everything else under the sun but not even once has someone tried to login as my admin user. It’s acting as more than a slightly longer password.