Overview
LLM Gateway Enterprise includes comprehensive security features for protecting your data, controlling access, and maintaining compliance.Authentication
Passkey Support
WebAuthn/FIDO2 passwordless authentication:- Phishing resistant
- No passwords to steal
- Biometric authentication
- Hardware security keys
- Better user experience
OAuth Integration
Supported providers:- GitHub - Enterprise SSO support
- Google - Workspace integration
Session Management
Secure session handling:- Encrypted session tokens
- HTTP-only cookies
- Secure flag in production
- SameSite protection
- Automatic expiration
API Key Security
Key Generation
API keys are cryptographically secure:Key Storage
- Keys hashed with bcrypt before storage
- Original key shown once at creation
- Only hash stored in database
- Keys validated via constant-time comparison
Key Rotation
Usage Limits
Per-key usage limits:Provider Key Security
Enterprise feature for managing provider API keys:Encryption
All provider keys encrypted at rest:- AES-256-GCM
- Unique IV per key
- Master key from environment
- Key rotation supported
Access Control
Only authorized services can access provider keys:- Gateway service: read-only access
- API service: read/write access
- UI: never has direct access
- Keys transmitted over TLS only
Network Security
TLS/SSL
All communication encrypted:CORS Configuration
Strict CORS policy:Access-Control-Allow-Origin: whitelisted origins onlyAccess-Control-Allow-Credentials: trueAccess-Control-Allow-Methods: GET, POST, PUT, DELETEAccess-Control-Max-Age: 86400
Rate Limiting
Protect against abuse:Data Security
Encryption at Rest
Database encryption:- PostgreSQL: transparent data encryption (TDE)
- Redis: encrypted backups
- File storage: AES-256 encryption
Encryption in Transit
All inter-service communication encrypted:Data Isolation
Multi-tenancy security:- Row-level security (RLS) in PostgreSQL
- Tenant ID in all queries
- Separate encryption keys per tenant
- No cross-tenant data leakage
Guardrails (Enterprise)
Content filtering and security rules.PII Detection
Automatically detect and redact:- Email addresses
- Phone numbers
- Social Security Numbers
- Credit card numbers
- IP addresses
- API keys
Jailbreak Detection
Detect prompt injection attempts:- Instruction hijacking
- Role confusion
- Context smuggling
- Delimiter injection
Secret Detection
Prevent API key leakage:Custom Rules
Create organization-specific rules:Audit Logging
Comprehensive audit trail for compliance.What’s Logged
Logged Actions
- Authentication (login, logout, failed attempts)
- API key operations (create, delete, rotate)
- Organization changes (settings, billing, members)
- Project operations (create, delete, update)
- Provider key management
- Subscription changes
- Data exports
- Admin actions
Retention
Audit logs retained:- Free: 30 days
- Pro: 90 days
- Enterprise: Configurable (default 1 year)
Compliance
Supports:- SOC 2 Type II
- GDPR Article 30
- HIPAA audit requirements
- PCI DSS logging
Secrets Management
Environment Variables
Secure secret handling:Docker Secrets
Kubernetes Secrets
External Secrets
Integrations:- AWS Secrets Manager
- Google Secret Manager
- Azure Key Vault
- HashiCorp Vault
Vulnerability Management
Dependency Scanning
Automated security scanning:Container Scanning
Penetration Testing
Enterprise customers receive:- Annual penetration tests
- Vulnerability reports
- Remediation guidance
- Re-testing after fixes
Compliance
SOC 2 Type II
- Security controls documented
- Audit logs maintained
- Access controls enforced
- Incident response plan
- Regular security reviews
GDPR
- Data processing agreement
- Right to access
- Right to deletion
- Data portability
- Privacy by design
HIPAA
- Business associate agreement
- Encrypted data at rest and in transit
- Audit logging
- Access controls
- Incident response
PCI DSS
- No credit card storage (Stripe handles)
- Encrypted transmission
- Access logging
- Security policies
- Regular testing
Incident Response
Security Contact
Report vulnerabilities:- Email: [email protected]
- PGP key: Available on request
- Response SLA: 24 hours
Incident Workflow
- Detection - Automated alerts or manual report
- Containment - Isolate affected systems
- Investigation - Determine scope and impact
- Remediation - Apply fixes and patches
- Communication - Notify affected customers
- Post-mortem - Document lessons learned
Breach Notification
Customers notified within:- 24 hours: Critical breaches
- 72 hours: GDPR requirement
- Regular updates until resolved
Security Checklist
Production Deployment
- Use strong passwords (16+ characters)
- Enable TLS/SSL everywhere
- Set secure
AUTH_SECRET - Configure CORS properly
- Enable rate limiting
- Use secrets management
- Enable audit logging
- Configure guardrails
- Set up monitoring
- Document security policies
- Train team on security
- Regular security audits
API Key Management
- Rotate keys regularly
- Set usage limits
- Monitor for anomalies
- Revoke unused keys
- Never commit keys to Git
- Use separate keys per environment
Access Control
- Follow least privilege principle
- Review permissions quarterly
- Enable 2FA for admins
- Audit user access
- Remove inactive users
Security Updates
Stay informed about security:- Subscribe to security newsletter
- Monitor GitHub security advisories
- Follow @llmgateway on Twitter
- Join community Slack channel
- Review CHANGELOG for security fixes