
I like write filters -> mostly immutable systems. SHTF? reboot ASAP.

I like write filters -> mostly immutable systems. SHTF? reboot ASAP.

Most shell users have enough privilege to read (exfiltrate) most data-value from a server, and they almost always have the capacity to damage it beyond functional operation.

It’s nice that your system has layers, but when the cutworms get on your onion they can still spoil the whole thing.

if an hostile actor gets a shell on your server, you are fucked anyway.
I keep telling EVERYONE this, and we continue to get “findings” around privilege escalation.

I’m going to take exception right here:
“Install Essential Administrative Tools”
The first thing you do to lock down a server is: Uninstall everything that is non-essential.
Do you need any wireless access to the server? If not, remove all WiFi, Bluetooth, and other wireless support from the kernel (block the modules).
Do you need anyone to be able to plug in a USB dongle that can bridge to ethernet? Or anything else?
Remove support for everything you don’t need first, un-necessary attack surface is the first foot-gun.
Are these administrative tools all essential? Keep / install what you need, sudo apt purge the rest.
Do you know WTF you’re doing with Docker containers and firewalls / iptables? The thing to do is learn how that really works, before getting your application servers / containers up on the open internet.
Do you know what un-necessary attack surfaces exist within your container images? That’s another step toward a hardened system - know what you’re running, know what that means, and
above all else: run as little as possible.
sudo is a great tool, for people who play nicely.
It’s like a lock on a glass door, with a rock garden outside.