Support controlled outbound access from sandboxes

Open
#3 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python

Research direction

Start by reading the sandbox command execution and production deployment configuration to locate where network access and runtime flags are controlled; the issue does not name specific files. Define the threat model, supported workloads, and server-owned destination and protocol policy, then document controls and audit events. Done means the design covers fail-closed enforcement and production verification, with integration tests for allowed destinations, denied destinations, and bypass attempts.

Written by the indexing model from the issue text.

Description

area: runner enhancement

Command sandboxes currently run without network access. Some future skills may need direct outbound access for workloads that cannot be covered by brokered tools. Define those use cases and the security boundary before enabling egress.

This is separate from brokered MCP and API execution. Brokered tools should not require opening sandbox networking.

Scope

  • Identify the workloads that require direct sandbox egress.
  • Design an explicit, server-owned destination and protocol policy.
  • Keep networking disabled by default and fail closed when enforcement is unavailable.
  • Prevent access to internal services, host services, and cloud metadata endpoints.
  • Address DNS rebinding, redirects, IPv4 and IPv6 destinations, and proxy bypasses.
  • Document operator controls and useful audit events.

Acceptance criteria

  • A design describes the threat model, enforcement mechanism, and supported use cases.
  • Repository input cannot select networks or alter runtime flags, mounts, or credentials.
  • Allowed destinations work, while denied destinations and bypass attempts fail in integration tests.
  • The production deployment documents how to verify that enforcement is active.
Dominant language
Python
Stars
1
Forks
1
Avg merge
1h 9m
Merged PRs (30d)
322

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from piotrekno1/second-shift

All issues in piotrekno1/second-shift

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.