Skip to main content

Overview

IncidentFox is built with enterprise security as a core principle. This document covers the security architecture, compliance certifications, and best practices for secure deployment.

Security Architecture

Credentials Proxy

Secrets never touch the agent. IncidentFox uses an Envoy-based credentials proxy:
  1. Agent makes API call through Envoy proxy
  2. Envoy intercepts the request
  3. Credential Resolver fetches secrets from vault
  4. Envoy injects credentials at request time
  5. Request is forwarded to external API
  6. Secrets are never stored in agent memory

Benefits

Claude Sandbox Isolation

The Claude SDK SRE Agent runs in isolated Kubernetes sandboxes:

gVisor Isolation

  • User-space kernel intercepts all syscalls
  • Reduced kernel attack surface
  • Container-to-host isolation

Network Policies

Resource Limits

  • CPU: Bounded to prevent runaway processes
  • Memory: Capped to prevent OOM attacks
  • Time: Maximum investigation duration
  • Ephemeral: Sandbox destroyed after use

Authentication

Token Types

SSO/OIDC Support

Supported identity providers:
  • Google Workspace
  • Azure AD / Entra ID
  • Okta
  • Generic OIDC

Configuration

Authorization (RBAC)

Roles

Tool-Level Permissions

Restrict access to sensitive tools:

Approval Workflows

For high-risk operations, require approval:

Approval Flow

  1. Agent proposes action
  2. Notification sent to approvers
  3. Approver reviews and approves/denies
  4. Action executed or cancelled

Audit Logging

All operations are logged:

Event Types

Log Format

Log Destinations

  • CloudWatch Logs
  • Datadog
  • Splunk
  • Custom webhook

Compliance

SOC 2 Type II

IncidentFox maintains SOC 2 Type II certification:

Data Handling

Deployment Security

Self-Hosted

For maximum control:
  • Deploy in your VPC
  • Use your secrets manager
  • Control all network egress
  • Manage your own keys

Air-Gapped

For highly restricted environments:
  • No external network access
  • Local model inference
  • Internal secrets management
  • Manual updates

Best Practices

Credential Management

  1. Use vault references, never plain text
  2. Rotate credentials regularly
  3. Use service accounts with minimal permissions
  4. Enable audit logging for secret access

Network Security

  1. Use private endpoints where possible
  2. Enable VPC peering for cloud services
  3. Restrict agent egress to necessary destinations
  4. Use TLS for all communications

Access Control

  1. Enable SSO for all users
  2. Use team-scoped tokens
  3. Require MFA for admin access
  4. Regular access reviews

Monitoring

  1. Alert on authentication failures
  2. Monitor for unusual tool usage
  3. Track investigation patterns
  4. Review audit logs regularly

Incident Response

Security Incidents

If you discover a security issue:
  1. Email security@incidentfox.ai
  2. Do not disclose publicly
  3. We will respond within 24 hours

Vulnerability Disclosure

We follow responsible disclosure:
  • 90-day disclosure timeline
  • Credit for reporters
  • Bug bounty program available

Next Steps

Configuration

Configure security settings

API Authentication

API authentication details