# Configure Network Security for Claude Code

AI coding sandboxes need clear network boundaries to reduce accidental exposure. This skill provides a structured workflow for trusted domains, access rules, validation, and documentation.

## Install

```bash
npx skillstore add dnyoussef/when-setting-network-security-use-network-security-setup
```

## Metadata

- Status: approved
- Slug: dnyoussef-when-setting-network-security-use-network-security-setup
- Skillstore revision: r1
- Version status: missing
- Tree hash: 51678d8ab97085a185d8d57301d8fcd9fb2a24c89f4db00f1df0a5148b00b34a
- Author: DNYoussef
- GitHub username: DNYoussef
- License: MIT
- Repository: https://github.com/DNYoussef/ai-chrome-extension/tree/main/.claude/skills/specialized-tools/when-setting-network-security-use-network-security-setup
- Ref: c579efd02184f1128d6741d16e6c8d951d7d4208
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/dnyoussef-when-setting-network-security-use-network-security-setup
- Manifest: https://skillstore.pages.dev/api/skills/dnyoussef-when-setting-network-security-use-network-security-setup/manifest

## Capabilities

- Documents required external dependencies, ports, protocols, and rate limits for a sandbox.
- Defines a whitelist-based network policy with trusted and blocked domains.
- Shows example firewall, DNS filtering, proxy, and environment variable configuration steps.
- Creates validation steps for trusted domain access, blocked domain checks, and local port checks.
- Produces deployment documentation for operators who maintain network security controls.

## Use Cases

- Prepare a Claude Code Sandbox Policy: Define allowed domains, blocked protocols, ports, and documentation before enabling network access for a development sandbox.
- Review CI Network Egress Controls: Map build dependencies to an allowlist and create repeatable tests for expected outbound access.
- Document Team Network Rules: Create clear network requirements, deployment notes, and maintenance checks for engineering teams using AI coding tools.

## Prompt Templates

### List Network Requirements

```
Use this skill to list the external domains, ports, protocols, and rate limits needed for my Claude Code sandbox.
```

### Create an Allowlist Policy

```
Use this skill to draft a whitelist network policy for a project that needs GitHub, package registries, and one internal API.
```

### Plan Safe Validation Steps

```
Use this skill to design network access tests that avoid contacting untrusted domains and preserve existing proxy settings.
```

### Audit a Proposed Configuration

```
Use this skill to review my planned firewall, DNS, proxy, and documentation changes before I apply them in a sandbox.
```

## Limitations

- The skill provides SOP guidance and example scripts, not a verified network security product.
- The examples may require administrator privileges and can disrupt host networking if run unchanged.
- The domain and port lists are generic and must be reviewed for each organization.
- The validation commands depend on local firewall, DNS, and proxy behavior.

## Best Practices

- Review every domain, port, and protocol against an approved business requirement before applying rules.
- Test firewall, DNS, and proxy changes in a disposable sandbox before using shared infrastructure.
- Keep rollback steps and audit notes with every network policy change.

## Anti Patterns

- Running generated firewall scripts on a workstation or shared server without review.
- Using public suspicious domains as live test targets for blocked access checks.
- Clearing proxy environment variables without confirming organizational egress requirements.

## Security Audit

- Audited at: 2026-07-05T14:00:34.288\+00:00
- Summary: Most static external-command detections are false positives caused by Markdown fences or inline code formatting. The real risks are the generated shell scripts, privileged host network changes, proxy environment modification, and a live blocked-domain test that may contact an untrusted domain if controls fail.

## Stats

- Views: 246
- Downloads: 6
- Favorites: 0
- Popularity score: 0