Security Best Practices
Agent Mesh Enterprise provides multiple security layers to protect your deployment. This guide covers authentication, authorization, network security, credential management, and operational security best practices.Security Architecture
Agent Mesh Enterprise implements defense-in-depth security:Security Layers
- Network Layer: TLS encryption, firewall rules, DDoS protection
- Authentication Layer: OAuth2, token validation, session management
- Authorization Layer: RBAC, scope enforcement, policy decisions
- Transport Layer: Secure broker messaging, certificate validation
- Data Layer: Credential management, encryption at rest, access control
Authentication Security
OAuth2 Configuration
Production Settings
Never use development mode in production:Disable Development Mode
Disable OAuth2 development mode:true) allows:
- HTTP connections (insecure)
- Relaxed token scope validation
- Insecure transport
Token Security
SAM Access Tokens
Configure secure token settings:- Token TTL: 1-4 hours (balance security vs. UX)
- Session timeout: Match or be shorter than token TTL
- Clock skew: Account for distributed systems (300s recommended)
- Secure cookies: Always
truein production - HttpOnly cookies: Prevent XSS attacks
- SameSite:
strictorlaxfor CSRF protection
Token Refresh
Implement automatic token refresh:Multi-Factor Authentication
Enforce MFA at the identity provider level: Azure AD:Authorization Security
RBAC Best Practices
Principle of Least Privilege
Grant minimum permissions required:Wildcard Usage
Minimize wildcard scopes:- Admin roles (documented and audited)
- Logical groupings (e.g.,
tool:data:*for data analysts)
Role Separation
Separate read/write permissions:Custom Tool Security
Enforce fine-grained access on custom tools:Agent Access Control
Restrict agent access per user:Network Security
TLS/SSL Configuration
Gateway HTTPS
Always use HTTPS in production:OAuth2 Service HTTPS
Broker TLS
Secure broker connections:Certificate Management
Let’s Encrypt Automation
Certificate Validation
Verify certificates before deployment:Firewall Configuration
Inbound Rules
Outbound Rules
CORS Configuration
Restrict Cross-Origin Resource Sharing:Credential Management
Environment Variables
Store secrets as environment variables:Docker Secrets
Use Docker secrets for sensitive data:Kubernetes Secrets
For Kubernetes deployments:Secret Rotation
Implement regular credential rotation:- OAuth2 secrets: Every 90 days
- Database passwords: Every 90 days
- API keys: Every 180 days
- SSL certificates: Automated (Let’s Encrypt)
Connector Security
Shared Credential Model
Understand connector security implications:Principle of Least Privilege
Configure minimal database permissions:API Key Scoping
Use scoped API keys for OpenAPI connectors:Operational Security
Audit Logging
Enable comprehensive audit logging:Security Monitoring
Monitor for security events:Rate Limiting
Implement rate limiting to prevent abuse:DDoS Protection
Implement DDoS mitigation:Compliance
Data Retention
Implement data retention policies:Encryption at Rest
Encrypt sensitive data:Privacy Controls
Implement privacy protections:Security Checklist
Pre-Production
- OAuth2 development mode disabled
- Authorization type set to
default_rbac - HTTPS enabled on all services
- Valid SSL certificates installed
- CORS restricted to specific origins
- Secrets stored in secrets manager
- Firewall rules configured
- Rate limiting enabled
- Audit logging enabled
- Security monitoring configured
Post-Deployment
- Regular security audits scheduled
- Credential rotation implemented
- Certificate renewal automated
- Backup procedures tested
- Incident response plan documented
- Security patches applied promptly
- Access reviews conducted quarterly
- Penetration testing performed annually
Incident Response
Security Incident Procedure
- Detect: Security monitoring alerts
- Contain: Disable compromised credentials
- Investigate: Review audit logs
- Remediate: Rotate secrets, patch vulnerabilities
- Document: Incident report
- Learn: Update security procedures
Emergency Lockdown
Procedure for security breach:Resources
Security Documentation
Security Tools
- Vulnerability Scanning: Trivy, Clair
- Secret Detection: GitGuardian, TruffleHog
- SIEM Integration: Splunk, ELK Stack
- Certificate Management: cert-manager (Kubernetes)
Next Steps
Authentication
Configure OAuth2 and RBAC
Connectors
Secure external data sources