Best Practices for Production Deployment

This section provides comprehensive security and operational best practices for deploying WSO2 Integrator: BI in production environments. Following these guidelines helps ensure your deployment is secure, resilient, and maintainable.

Runtime security

Runtime security focuses on securing your BI application and the services it generates during execution, including application-level configurations, patches, secrets management, TLS/SSL protocols, and logging.

Learn more about runtime security →

OS level security

Operating system security addresses the hardening of the underlying operating system where BI is deployed, covering user accounts, firewalls, SSH configuration, system updates, and monitoring.

Learn more about OS level security →

Network level security

Network security covers the infrastructure and network-level protections for your BI deployment, including high availability, failover configurations, network logging, port auditing, and device security.

Learn more about network level security →

Configuration best practices

Adhering to secure configuration practices is essential for minimizing vulnerabilities in your BI deployment. This includes managing sensitive data, applying security patches, and following secure coding standards.

Learn more about configuration best practices →

Keystore and truststore configuration

Keystores and truststores are essential for securing TLS/SSL communication in production. This guide covers how to create and manage keystores and truststores, and how to configure them in BI for HTTPS listeners, mutual TLS, and outbound client connections.

Learn more about keystore and truststore configuration

Getting started

Review each category above to understand the security considerations for your deployment. Implement these practices based on your specific environment, compliance requirements, and security policies. These guidelines are applicable to both cloud-native (containerized) and traditional VM-based deployments.