Started off by
- Enabling unattended updates
- Enable only ssh login with key
- Create user with sudo privileges
- Disable root login
- Enable ufw with necessary ports
- Disable ping
- Change ssh default port 21 to something else.
Got the ideas from networkchuck
Did this on the proxmox host as well as all VMs.
Any suggestions?
Anything that has internet access like your IoT can be C&C utilizing stateful connections. An outbound socket is built, and reflected traffic can come back in. Your IoT devices especially should not be exposed to the internet. They can’t even have an antivirus agent installed on them.
True, and 100% agree except I forgot to mention
1.) The fortigate has a known list of botnet command and control servers that are blocked 2.) I only allow them to access their home server domain names for the only purpose of allowing for firmware updates. They are not capable of accessing any other domains or IPs
That’s actually no longer true… kinda. You can’t install AV on them, but there are security companies filling the niche of embedded IoT security. Now, you won’t see this in your average consumer device, but on the commercial market there is a growing demand for some way to secure an embedded device from malicious software/firmware modifications.
You can SPAN internal traffic to an IDS device currently. Or, if internal network throughput isn’t an issue, you can force east-west traffic through an IPS with DPI enabled instead.
That’s historically how east-west would be mediated within an enterprise environment for devices incapable of being secured with agents.
Absolutely, and I’ve implemented similar east-west controls (as either prevent-first or for detection). You’ll get no argument from me on that. I’m just noting an interesting trend as IoT devices become more ubiquitous in commercial and industrial environments, and some of those devices must (for whatever reason) have access to some part of the network or internet.