3 ms·
Personally I would rather we just lean more into microVMs. From a cloud computing perspective, I don't care what security Linux claims to have, because I just a
by 0xbadcafebee 4y ago
Personally I would rather we just lean more into microVMs. From a cloud computing perspective, I don't care what security Linux claims to have, because I just assume it is ineffective and move forward from there. We build systems using loosely-coupled, strongly-authenticated, temporary sessions, and it's very easy to enforce separation of concerns (and thus minimize attack surface).
- staticassertion 4y agoIt would be nice to have a more trustworthy stack at every ring, I think.
- slt2021 4y agoyour code may be secure, but your cloud neighbor or VM host may be not. if VM host machine is taken over, then your VMs are at risk too https://unit42.paloaltonetworks.com/azure-container-instances/ https://unit42.paloaltonetworks.com/azure-container-instance...
- 0xbadcafebee 4y agoTrue, but it's pretty rare for hypervisors to be exploited. In that Azure case the node itself maintained a connection to each VM, which kind of defeats the purpose of using VMs for isolation.... It's like having strong memory guarantees in Linux and then having an open socket from a root-owned process to every other process... like, maybe giving them a new attack vector to a SPOF isn't a great idea
- slt2021 4y agohypervisor exploitation exist, just as container escapes and every other runtime escape and escalation. Which is natural for cloud native app development. remember the shared security model, the lower stack of infra depends on cloud vendor, and it critically depends on hypervisor/OS/container runtime security and configuration hardening
- fsflover 4y agoIf you care about security, Qubes OS is more secure, with its hardware virtualization: https://qubes-os.org https://qubes-os.org.