Skip to content

sandboxes/policy: document blocked values for user-defined rules #24611

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dvdksn merged 1 commit into from
Apr 3, 2026
+11 −0
Merged

sandboxes/policy: document blocked values for user-defined rules #24611

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions content/manuals/ai/sandboxes/security/policy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,6 +60,17 @@ and denies `*.corp.internal`:
- `sbx policy allow network build.corp.internal` — no effect, because the
organization denies `*.corp.internal`

#### Blocked values in user-defined rules

To prevent overly broad rules from undermining the organization's policy,
certain catch-all values are blocked in user-defined rules:

- Domain patterns: `*`, `**`, `*.com`, `**.com`, `*.*`, `**.**`
- CIDR ranges: `0.0.0.0/0`, `::/0`

Scoped wildcards like `*.example.com` are still allowed. If you attempt to
use a blocked value, `sbx policy` returns an error immediately.
Copy link
Copy Markdown
Contributor

@chrispatrick chrispatrick Apr 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it worth noting that creation of the rules is blocked, but if the user already has blocked values in their local policy then they are ignored? Or maybe that is edge-case enough to ignore?

Copy link
Copy Markdown
Contributor Author

@dvdksn dvdksn Apr 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was thinking about it, but it sort of goes down into a rabbit hole of, "but if it's blocked, how could be set in the first place?", and then we'd have to explain that too...

So... it's not totally unreasonable to mention this edge case. But wasn't sure it was worth it. Let's maybe see if it comes up.


## Network policies

The only way traffic can leave a sandbox is through an HTTP/HTTPS proxy on
Expand Down