A Secure Environment for Untrusted Helper Applications¶
Goldberg, I., Wagner, David, Thomas, Randi, & Brewer, E. A. (1996). A Secure Environment for Untrusted Helper Applications: Confining the Wily Hacker. Proceedings of the 6th USENIX Security Symposium.
Cited by¶
2 citations across 2 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Innovation Sandbox
- Software and security: process-level sandboxes (browser tabs, OS containers, syscall jails), language-level sandboxes (WASM, JavaScript VMs), staging environments separated from production.
This sourceFoundational system-call-confinement (Janus) sandbox isolating untrusted code from the host.
Supported in partVerified against the work's full text
Defines sandboxing as confining a helper application to a restricted environment and implements it as a process-level, system-call-filtering jail; it does not cover containers, WASM or JavaScript VMs, or staging environments.
“W eu s e t h e t erm sandb oxing t od es c ri be t h e concept of con/ n/- in ga h elp er ap plica t ion t o a re str ict ed e n vironm en t”
- Software and security: process-level sandboxes (browser tabs, OS containers, syscall jails), language-level sandboxes (WASM, JavaScript VMs), staging environments separated from production.
- Sandboxing
- The combination is the load-bearing commitment: pure containment (a vault, a quarantine) suppresses; pure exercise (production deployment) exposes; sandboxing does both at once by tightly specifying which actions the contained process may perform on the outside and which it may not.
This sourceIntroduces a sandbox that confines an untrusted process by interposing on and restricting the system calls it may make on the outside.
Supported in partVerified against the work's full text
Goldberg et al. confine an untrusted helper by restricting its access to the OS through filtered system calls, which is the specified-permitted-actions side of the claim.
“W ep r o po se t or e d u ce t h er i s k of a s ecur it y breac hb y re str ict in gt h e program/'s ac/- ce ss t ot h eo pe r a t in g syst em/.”
- The combination is the load-bearing commitment: pure containment (a vault, a quarantine) suppresses; pure exercise (production deployment) exposes; sandboxing does both at once by tightly specifying which actions the contained process may perform on the outside and which it may not.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Read against the text for 2 of 2 citations: 2 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Was it audited? Yes. A second, independent pass read the citation against the article text and recorded a verdict.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Links previously used in the corpus¶
Before the registry existed this work was also linked 1 other way.
Registry ID ref:c03a4f1812bd · see in the full table