Started off by

  1. Enabling unattended updates
  2. Enable only ssh login with key
  3. Create user with sudo privileges
  4. Disable root login
  5. Enable ufw with necessary ports
  6. Disable ping
  7. 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?

  • tango_suckah@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    They can’t even have an antivirus agent installed on them.

    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.

    • radiantxero@alien.topB
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      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.

      • tango_suckah@alien.topB
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        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.