2 ms·
I think there is definitely a need for some work in this space.. but the fact is, there are a LOT of databases open to the wild. These are just the ones that d
by tracker1 10y ago
I think there is definitely a need for some work in this space.. but the fact is, there are a LOT of databases open to the wild. These are just the ones that didn't bother to set an admin password. They also didn't setup any firewall rules.
0. upload client public key
1. Setup SSH auth by cert/key
2. Move SSH to non-standard port
3. Enable passwordless sudo
4. Disable password auth
5. Setup firewall to only allow the new ssh port
6. Setup port knocking
Those are the first few things I do on a server... As locked down as I can get before doing anything else... of course, I'll also put the new ssh port and an alias in my ~/.ssh/config ...
Most cloud providers offer the option to have a "private" IP space... just having a proper firewall ufw/ipchains/iptables, etc config can go a long way towards helping lock things down.
Of course, that only goes so far when you aren't using passwords or TLS for client/server communications. But it's better than leaving the front door open with a sign saying as much.