Learn about Claude Code's security safeguards and best practices for saf 9203 e usage.

Your code's security is paramount. Claude Code is built with security at its core, developed according to Anthropic's comprehensive security program. Learn more and access resources (SOC 2 Type 2 report, ISO 27001 certificate, etc.) at Anthropic Trust Center.

Claude Code uses strict read-only permissions by default. When additional actions are needed (editing files, running tests, executing commands), Claude Code requests explicit permission. Users control whether to approve actions once or allow them automatically.

We designed Claude Code to be transparent and secure. For example, we require approval for bash commands before executing them, giving you direct control. This approach enables users and organizations to configure permissions directly.

For detailed permission configuration, see Identity and Access Management.

To mitigate risks in agentic systems:

• Sandboxed bash tool: Sandbox bash commands with filesystem and network isolation, reducing permission prompts while maintaining security. Enable with /sandbox to define boundaries where Claude Code can work autonomously
• Write access restriction: Claude Code can only write to the folder where it was started and its subfolders—it cannot modify files in parent directories without explicit permission. While Claude Code can read files outside the working directory (useful for accessing system libraries and dependencies), write operations are strictly confined to the project scope, creating a clear security boundary
• Prompt fatigue mitigation: Support for allowlisting frequently used safe commands per-user, per-codebase, or per-organization
• Accept Edits mode: Batch accept multiple edits while maintaining permission prompts for commands with side effects

Claude Code only has the permissions you grant it. You're responsible for reviewing proposed code and commands for safety before approval.

Prompt injection is a technique where an attacker attempts to override or manipulate an AI assistant's instructions by inserting malicious text. Claude Code includes several safeguards against these attacks:

• Permission system: Sensitive operations require explicit approval
• Context-aware analysis: Detects potentially harmful instructions by analyzing the full request
• Input sanitization: Prevents command injection by processing user inputs
• Command blocklist: Blocks risky commands that fetch arbitrary content from the web like curl and wget by default. When explicitly allowed, be aware of permission pattern limitations

We have implemented several safeguards to protect your data, including:

• Limited retention periods for sensitive information (see the Privacy Center to learn more)
• Restricted access to user session data
• User control over data training preferences. Consumer users can change their privacy settings at any time.

For full details, please review our Commercial Terms of Service (for Team, Enterprise, and API users) or Consumer Terms (for Free, Pro, and Max users) and Privacy Policy.

• Network request approval: Tools that make network requests require user approval by default
• Isolated context windows: Web fetch uses a separate context window to avoid injecting potentially malicious prompts
• Trust verification: First-time codebase runs and new MCP servers require trust verification
  • Note: Trust verification is disabled when running non-interactively with the -p flag
• Command injection detection: Suspicious bash commands require manual approval even if previously allowlisted
• Fail-closed matching: Unmatched commands default to requiring manual approval
• Natural language descriptions: Complex bash commands include explanations for user understanding
• Secure credential storage: API keys and tokens are encrypted. See Credential Management

Best practices for working with untrusted content:

1. Review suggested commands before approval
2. Avoid piping untrusted content directly to Claude
3. Verify proposed changes to critical files
4. Use virtual machines (VMs) to run scripts and make tool calls, especially when interacting with external web services
5. Report suspicious behavior with /bug

Claude Code allows users to configure Model Context Protocol (MCP) servers. The list of allowed MCP servers is configured in your source code, as part of Claude Code settings engineers check into source control.

We encourage either writing your own MCP servers or using MCP servers from providers that you trust. You are able to configure Claude Code permissions for MCP servers. Anthropic does not manage or audit any MCP servers.

See here for more information on the security of running Claude Code in an IDE.

When using Claude Code on the web, additional security controls are in place:

• Isolated virtual machines: Each cloud session runs in an isolated, Anthropic-managed VM
• Network access controls: Network access is limited by default and can be configured to be disabled or allow only specific domains
• Credential protection: Authentication is handled through a secure proxy that uses a scoped credential inside the sandbox, which is then translated to your actual GitHub authentication token
• Branch restrictions: Git push operations are restricted to the current working branch
• Audit logging: All operations in cloud environments are logged for compliance and audit purposes
• Automatic cleanup: Cloud environments are automatically terminated after session completion

For more details on cloud execution, see Claude Code on the web.

• Review all suggested changes before approval
• Use project-specific permission settings for sensitive repositories
• Consider using devcontainers for additional isolation
• Regularly audit your permission settings with /permissions

• Use enterprise managed policies to enforce organizational standards
• Share approved permission configurations through version control
• Train team members on security best practices
• Monitor Claude Code usage through OpenTelemetry metrics

If you discover a security vulnerability in Claude Code:

1. Do not disclose it publicly
2. Report it through our HackerOne program
3. Include detailed reproduction steps
4. Allow time for us to address the issue before public disclosure

• Sandboxing - Filesystem and network isolation for bash commands
• Identity and Access Management - Configure permissions and access controls
• Monitoring usage - Track and audit Claude Code activity
• Development containers - Secure, isolated environments
• Anthropic Trust Center - Security certifications and compliance