Use NGINX as a Reverse Proxy to the Cortex XSOAR engines.
NGINX can act as a reverse proxy that sits between internal applications and external clients, forwarding client requests to the appropriate application. Using NGINX as a reverse proxy in front of the engine enables you to provide network segmentation where the proxy can be put on a public subnet (DMZ) while the engine can be on a private subnet, only accepting traffic from the proxy. Additionally, NGINX provides a number of advanced load balancing and acceleration features that you can utilize.
The following topics describe how to install NGINX, how to use a Self-Signed Certificate for non-production environments, and how to configure NGINX.
Use Engines Through the NGINX Reverse Proxy
If you want to use an engine (d1) through the reverse proxy, you need to modify
EngineURLs in the
d1.conf file to point to the host and port the NGINX server is listening on.