Security and best practices for environments
When deploying environments with NetFoundry, following best practices ensures optimal security, performance, and manageability. This page shows key recommendations for managing your environments effectively.
Environment security
- Unique identity: Each environment receives a cryptographically secure identity that can't be spoofed or replicated.
- Encrypted communication: All traffic between your environment and NetFoundry's network is encrypted end-to-end.
- Zero trust architecture: Environments operate on zero-trust principles—no implicit trust is granted based on network location.
Deployment best practices
- Strategic placement: Deploy Frontdoor agents (and create environments) close to your backend services to minimize latency.
- Descriptive naming: Use clear, descriptive names for your environments to make management easier:
production-web-serverdevelopment-api-gatewaystaging-database-proxy
- Resource planning: Consider the resource requirements of your backend services when planning environment deployment.
- Monitoring: Regularly review environment metrics to understand usage patterns and performance.
Environment lifecycle management
- Regular review: Periodically review your environments to identify unused or outdated instances.
- Proper cleanup: Delete environments that are no longer needed to maintain security and reduce complexity.
- Documentation: Maintain documentation about what services each environment supports and its purpose.