SEP-1: A Sole-Egress Package-Broker Profile for Model-Evaluation Sandboxes
Zhixuan Xu (George) · Team UWaterloo
Submitted to AI Incident Response Sprint. Sprint projects are early-stage work by participants, not Apart Research publications.
In July 2026, the OpenAI→Hugging Face escape left the sandbox through the only network exit it was allowed to have: the package-registry proxy. The egress policy never even fired, because it was watching destinations, not payloads. Where the sandbox connected looked fine. What actually crossed the boundary didn't matter to it.
SEP-1 is our attempt at a containment standard that drops the allowed-destination model altogether. Instead of a network, the sandbox gets a socket. A broker on the other side serves only pre-resolved, hash-pinned packages, and the sandbox itself has no network interface at all — nothing to route, nothing to escape through.
To test this, we built a harness and ran the same 12-attack suite twice, once against an allowlist setup and once against SEP-1, with a compromised upstream in both cases. The results were lopsided. Under the allowlist, 11 of the 12 attacks made it across the boundary — and the policy monitor still called 13 of 14 connections "in-policy." SEP-1 contained 11 of 12. The twelfth degrades into a covert channel, which we measured and bounded: 216,000 bits/hour worst case, and roughly 15 bits per sandbox lifetime once caching kicks in.
Each run ends in a hash-chained conformance report. A third party can verify it against the public lockfile and probe suite without touching the lab's network. An allowlist log can't give you that, and we think this auditability — not the attack numbers alone — is what makes the standard something a regulator could actually check and adopters could actually trust.
Reviews
The project presents a concrete package-broker design that restricts retrieval to approved, hash-pinned artifacts. Its mock-upstream comparison reports containment of 11 of 12 probes while preserving legitimate retrieval and exposing a residual communication channel. The design has practical potential, but its leakage bounds and deployment guarantees need further validation.
Strength: Restricting the sandbox to approved artifacts addresses a concrete weakness in destination-based controls. The successful legitimate-fetch test makes the design more useful by showing that containment can preserve an intended function.
Recommendation:
- Define the security promise precisely. Blocking arbitrary downloads and preventing sensitive information from leaving are different guarantees. The remaining request channel makes that distinction consequential: the caching estimate considers ordering, while request timing may reveal additional information. Define the complete observable channel and explain what level of leakage is acceptable for the intended evaluation. This would turn the reported bound into a meaningful security assurance.
- Demonstrate the guarantee in the deployment being proposed. The committed results use in-process orchestration, while the design relies on enforced network isolation. An end-to-end container demonstration that preserves legitimate retrieval while denying other network access would provide stronger evidence that the profile works as an operational containment control.
Read full reviewShow less
This project effectively eliminates egress escapes by removing virtual network interfaces entirely and relying solely on a Unix Domain Socket (UDS) governed by SEP-1's eight validation rules (pinned SHA hashes, size checks, and redirect blocking). It is an elegant architectural shift, though I wonder how cleanly this will scale across high-concurrency workloads and distributed multi-node clusters. That said, trading a slight latency hit at startup for deterministic AI containment is an entirely reasonable compromise
SEP-1 addresses a practical problem because evaluation agents may need software packages without needing unrestricted internet access. It proposes choosing approved package versions in advance and making them available through a restricted service. That could reduce opportunities for agents to communicate outside the evaluation while preserving useful work.
The claimed limits on communication need stronger support. An agent could communicate through when it requests packages, not just which packages it chooses. The report also needs to make clearer which protections were implemented and which remain proposed. I would compare a realistic package dependent task under SEP-1 with the same task using preinstalled packages and no network access. That would help establish whether the extra service offers enough benefit to justify its complexity.
Cite this project
@misc{george2026sep1,
title = {{SEP-1: A Sole-Egress Package-Broker Profile for Model-Evaluation Sandboxes}},
author = {Zhixuan Xu (George)},
year = {2026},
month = sep,
note = {Submitted to AI Incident Response Sprint, an Apart Research Sprint},
howpublished = {\url{https://apartresearch.com/sprints/projects/sep1-a-soleegress-packagebroker-profile-for-modelevaluation-sandboxes-7kif}},
url = {https://apartresearch.com/sprints/projects/sep1-a-soleegress-packagebroker-profile-for-modelevaluation-sandboxes-7kif}
}More from AI Incident Response Sprint
- View project: Adaptive AI-Based Containment of Autonomous Cyber Attacks: A Reproducible Docker Cyber Range Study
Adaptive AI-Based Containment of Autonomous Cyber Attacks: A Reproducible Docker Cyber Range Study
Saarlanders
The study evaluates whether an incident-history-reasoning defender outperforms a fixed response policy against an autonomous LLM attacker changing paths after containment. Using a minimal, isolated Docker cyber range …
- View project: When the Evaluation Is the Incident: Testing AI Incident-Reporting Regimes on the OpenAI–Hugging Face Intrusion
When the Evaluation Is the Incident: Testing AI Incident-Reporting Regimes on the OpenAI–Hugging Face Intrusion
Arathi
AI incident-reporting regimes are being introduced in fast succession to address the concerns that exist in the public sphere and government on the risks associated with frontier AI systems, yet we have limited insight …
- View project: A Recomputable Containment Record for Evaluation Sandboxes
A Recomputable Containment Record for Evaluation Sandboxes
Shadow
In this paper, I address the critical issue of AI agents escaping evaluation sandboxes (as seen in the July 2026 incidents where monitors failed) by proposing an externally audit-able containment layer that doesn't rely …