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
[–] 12 points 2 days ago (5 children)

Of course privilege escalation exists, but why roll out the red carpet on an attacker that managed to get shell access? Maybe in the time that they take to figure out that privilege escalation you have the time to detect the attack and defend against them

  • source
  • parent
  • hideshow 5 child comments
  • [–] 9 points 2 days ago (3 children)

    If someone put a script on your server that tried to do privilege escalation you should just assume it was successful and act accordingly. It doesn’t really change what should happen.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 3 points 2 days ago (2 children)

    replacing or reimaging it automatically when you see something like this feels like overkill.

  • source
  • parent
  • hideshow 2 child comments