4 ms·
There is a glaring omission from the possible attacks: the kernel itself provides a huge surface area and local root exploits are not uncommon. Speaking as an
by mocko 11y ago
There is a glaring omission from the possible attacks: the kernel itself provides a huge surface area and local root exploits are not uncommon.
Speaking as an infrastructure/devops/hosting consultant - I've done a couple of Docker deployments lately and clients often ask whether it's suitable for hosting multiple semi-trusted codebases on the same metal for better resource utilization. I tell them "no": once a competent attacker has shell they will not find it hard to escape the sandbox and take over the parent machine, and with it all other hosts. Docker is a great tool for rapid deployment, dependency management and dense hosting of microservices but security was never the primary goal.
Hypervisor based virtualization solutions (e.g. Xen, VMWare) expose a much smaller attack surface to the child environment. I would therefore say that while more resource intensive they are a far safer way to spin up honeypots.
- task_queue 11y agoI'd say spin up the VMs on a machine that doesn't matter if you're attracting automated attacks. If you wake up one morning to an exploit being discovered and have an unpatched host machine, is it still a honeypot?