Community identifies sandboxing as critical missing defense
3 Sep 19 6:21 PM · 4d ago · 11 comments · 1 source · development 3 of 5
Discussion shifts to operating system sandboxing as an inadequate defense. Multiple researchers argue that consumer OSes lack usable, documented sandboxing—and that capability-based security models (used in Android and iOS pickers but rarely elsewhere) should replace the identity-based model where processes run "as you" with full authority.
“I would like to be able to run a process in a way that prevents it from digging around in my home directory and exfiltrating anything it finds to someone else over the internet. This is way harder than it should be.”
simonwapropos (author of Datasette) Security researcher, post authorSimon Willison (simonw) Datasette maintainer, open-source security expertZ.ai Co. (formerly Zhipu AI) AI model developerjfred (commenter) Security architecture discussantDeAlignAI Model abliteration group
The whole story postscomments the bright band is this development · numbered dots are the others · click one to jump
What people said 11 voices · verbatim
-
I would like to see a whole lot more attention paid to sandboxing. It infuriates me that consumer operating systems don't ship with clearly documented, usable sandboxing features - the sandboxes they include today may as well have signs pasted on them saying "Beware of the Leopard". I would like to be able to run a process in a way that prevents…
-
I remain convinced that the right answer for desktop OSes in the long term (albeit not necessarily one that's easy to get to from here) will have to involve [capabilities](http://habitat-chronicles.com/2017/05/what-are-capabilities/comment-page-1/). The identity-based model of processes that run "as you" with all your authority hasn't really fit…
-
If we can figure out how to wrap that in a UI that doesn't require half a degree in cybersecurity to use safely and effectively I'm all for it!
-
It's worth considering the degree to which [need-to-know policies](https://en.wikipedia.org/wiki/Need_to_know), [compartmentalization](https://en.wikipedia.org/wiki/Compartmentalization_(information_security)), and [principles of least authority/access/privilege](https://en.wikipedia.org/wiki/Principle_of_least_privilege) are already successfully…
-
I'd say Docker, but everyone warns against using Docker as a sandbox. I've not fully evaluated the new [Docker Sandboxes](https://docs.docker.com/ai/sandboxes/) thing yet, though it seems very focused on coding agents and I want to use it for other stuff, too. Firecracker is a LONG way from being a user-friendly piece of software to install and…
-
You might find gVisor to be of interest.
-
> My problem with sandboxes is that what I really want is an easy-to-use sandbox from a company with a dedicated security team that works on that sandbox product, and who risk millions (ideally billions) of dollars if it leaks. same, and this is what draws me to Firecracker, it being developed by Amazon for AWS Lambda. It has a very restricted…
-
I haven’t read the article yet but I’ve had very similar thoughts: - we should assume that for the foreseeable future the rate of disclosure of critical vulnerabilities is going to be much higher, and we should be building systems with this in mind; and - I wonder if this is what finally causes software engineering to be regulated like other kinds…
-
Interesting... gVisor is entirely maintained by Google (they first released it in 2018) but I just saw that [two weeks ago](https://github.com/cncf/sandbox/issues/521) they started the process to donate it to CNCF.
-
I just use [a separate Linux user and Linux ACLs](
-
Forget easy to use, are there any actually hardened VM tools for anybody to use, even hard-to-setup ones? Like running a container in a hardened VM on linux. The best I found is firecracker and kata containers on Linux, but kata itself opens up a lot and I’ve been trying to harden that as well. The maintainers are really nice but it’s a lot of…
All 5 developments of Open-weight AI models trigger year-long security crisis →
Lobsters