A TOPIC, IN CONTEXT

trust boundary design

Judgments in this source concerning trust boundary design. Explore 1 viewpoint with evidence from 1 source.

1 people · 1 sources · 1 viewpoints

Content updated:

Explore connections ↗

Viewpoint map

Explore by person. Select two or three to compare.

1 people · 1 sources · 1 viewpoints

Olivia Johnston

Existing isolation uses an outdated unit of trust

Johnston says technologies such as gVisor and Firecracker isolate the platform from users and users from one another. She calls that unit of trust outdated and asks how to protect users from their “own” code.

Supporting evidence

Sidecars: A low-latency trust boundary for Sandboxes | Modal Blog

Original excerpt

technologies like gVisor and Firecracker “solved” “isolation” nearly eight years ago. Unfortunately for us, they solved it for an now-outdated unit of trust. How do you protect users from their “own” code?
Context

At Modal, our customers rely on Sandboxes to execute untrusted code written by their downstream users or, almost exclusively now, by agents. Running untrusted code isn’t a new problem: every cloud provider has to do this from day 1 to isolate their platform from their user and their users from each other. Fortunately,

Share insightCheck this claim

These are individual perspectives, not a measure of consensus. Source material stays in its original language.