Security Checklist
Critical
- Use
STRICTsecurity level for untrusted code - Enable AI Scoring Gate
- Set memory limits
- Configure timeouts
- Validate all tool inputs
- Run as non-root user
Recommended
- Enable end-to-end encryption
- Implement rate limiting
- Use network segmentation
- Enable audit logging
- Set up intrusion detection
- Regular security updates
Security Levels
Always use the appropriate security level:| Level | Use Case | Restrictions |
|---|---|---|
STRICT | Untrusted AI/user code | Maximum restrictions |
SECURE | Semi-trusted automation | High restrictions |
STANDARD | Internal tools | Moderate restrictions |
PERMISSIVE | Testing only | Minimal restrictions |
Defense in Depth
Layer 1: Input Validation
Validate code before it reaches Enclave:Layer 2: Pre-Scanner
Block obvious attacks early:Layer 3: AST Validation
Strict AST validation:Layer 4: AI Scoring Gate
Detect suspicious semantic patterns:Layer 5: Runtime Isolation
Maximum runtime isolation:Layer 6: Output Sanitization
Sanitize all outputs:Tool Security
Input Validation
Always validate tool inputs:Permission Control
Implement tool permissions per user:Data Filtering
Filter sensitive data from tool responses:Network Security
Isolation
Run Enclave in isolated network:TLS Configuration
End-to-End Encryption
Enable E2E encryption for sensitive data:Rate Limiting
Per-User Limits
Per-Tool Limits
Audit Logging
Comprehensive Logging
Log Retention
Container Security
Dockerfile Best Practices
Security Context
Secrets Management
Environment Variables
Never hardcode secrets:Kubernetes Secrets
Incident Response
Detection
Monitor for anomalies:Response Plan
- Detect - Automated monitoring alerts
- Contain - Isolate affected components
- Investigate - Review audit logs
- Remediate - Fix vulnerability
- Recover - Restore normal operation
- Learn - Post-incident review
Related
- Security Model - Architecture overview
- AI Scoring - Semantic analysis
- Production Deployment - Deployment guide