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:- Agent makes API call through Envoy proxy
- Envoy intercepts the request
- Credential Resolver fetches secrets from vault
- Envoy injects credentials at request time
- Request is forwarded to external API
- Secrets are never stored in agent memory
Benefits
| Traditional Approach | IncidentFox Approach |
|---|---|
| Agent stores secrets | Secrets in proxy only |
| Risk of memory exposure | Isolated credential handling |
| Static credentials | Dynamic credential injection |
| Audit gaps | Full audit trail |
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
| Type | Format | Scope | Expiration |
|---|---|---|---|
| Global Admin | ADMIN_TOKEN env var | Full access | Never |
| Org Admin | {org_id}.{random} | Organization | Configurable |
| Team Token | {org_id}.{team_id}.{random} | Team only | Configurable |
| OIDC JWT | Standard JWT | User session | Short-lived |
SSO/OIDC Support
Supported identity providers:- Google Workspace
- Azure AD / Entra ID
- Okta
- Generic OIDC
Configuration
Authorization (RBAC)
Roles
| Role | Permissions |
|---|---|
| Viewer | Read investigations, view dashboards |
| Operator | Trigger investigations, view all data |
| Admin | Configure tools, manage team settings |
| Org Admin | Manage teams, configure org settings |
Tool-Level Permissions
Restrict access to sensitive tools:Approval Workflows
For high-risk operations, require approval:Approval Flow
- Agent proposes action
- Notification sent to approvers
- Approver reviews and approves/denies
- Action executed or cancelled
Audit Logging
All operations are logged:Event Types
| Event | Logged Data |
|---|---|
| Investigation started | User, query, timestamp |
| Tool executed | Tool name, parameters, result status |
| Data accessed | Data source, query, row count |
| Configuration changed | Old value, new value, user |
| Approval requested/granted | Action, approver, decision |
Log Format
Log Destinations
- CloudWatch Logs
- Datadog
- Splunk
- Custom webhook
Compliance
SOC 2 Type II
IncidentFox maintains SOC 2 Type II certification:| Control | Implementation |
|---|---|
| Access Control | RBAC, SSO, MFA |
| Encryption | TLS 1.3, AES-256 at rest |
| Logging | Comprehensive audit trail |
| Monitoring | Real-time alerting |
| Incident Response | Documented procedures |
Data Handling
| Data Type | Handling |
|---|---|
| Investigation queries | Logged, retained 90 days |
| Tool results | Not stored (passed through) |
| Credentials | Never stored in agent |
| Audit logs | Retained per policy |
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
- Use vault references, never plain text
- Rotate credentials regularly
- Use service accounts with minimal permissions
- Enable audit logging for secret access
Network Security
- Use private endpoints where possible
- Enable VPC peering for cloud services
- Restrict agent egress to necessary destinations
- Use TLS for all communications
Access Control
- Enable SSO for all users
- Use team-scoped tokens
- Require MFA for admin access
- Regular access reviews
Monitoring
- Alert on authentication failures
- Monitor for unusual tool usage
- Track investigation patterns
- Review audit logs regularly
Incident Response
Security Incidents
If you discover a security issue:- Email security@incidentfox.ai
- Do not disclose publicly
- We will respond within 24 hours
Vulnerability Disclosure
We follow responsible disclosure:- 90-day disclosure timeline
- Credit for reporters
- Bug bounty program available

