4 ms·
At the moment, we manually verify operators and are currently onboarding some tier-4 operators. Down the line, we'll have a 2-tier system where you can choose w
by lschneider 2y ago
At the moment, we manually verify operators and are currently onboarding some tier-4 operators. Down the line, we'll have a 2-tier system where you can choose whether you want a verified machine or not. From the operator's perspective, everything runs inside Docker, configured with security best-practices.
- lolinder 2y agoI've always understood that containers are not proper sandboxes and shouldn't be used for containing untrusted code, no matter the best practices used. Has this changed in recent years? Do you have documentation for what sorts of best practices you're using and why they are sufficient for executing untrusted code?
- gavindean90 2y agoYou are correct from my knowledge. I would expect that if the container is set to not run as root you might be able to enforce fine meaningful security but I’d still run it in a VM if feasible.
- janosdebugs 2y agoHaving done a little bit of work in the area[1], I think you should publicly document exactly what those best-practices are. Are the workloads running in a networkless container? Do you limit IO? Do you limit disk usage? Answering these in detail would help you gain customer trust on both sides. [1]: https://containerssh.io/v0.5/reference/docker/#securing-docker https://containerssh.io/v0.5/reference/docker/#securing-dock...
- flaminHotSpeedo 2y agoSo you don't have real security for operators, is what you're saying. Containers are not, and will never be, a secure isolation boundary.