Configure the engine to use a web proxy - Configure a Cortex Cloud engine to use a web proxy by editing the d1.conf file. - Administrator Guide - Cortex XSIAM - Cortex CLOUD - Cortex - Security Operations

Cortex Cloud Runtime Security Documentation
Product
Cortex Cloud Application Security > Cortex CLOUD
License
Cloud Runtime Security
Creation date
2024-12-24
Last date published
2026-06-16
Category
Administrator Guide
Abstract

Configure a Cortex Cloud engine to use a web proxy by editing the d1.conf file.

Proxy settings can be configured in an engine by adding them as an engine configuration.

Note

You need to configure Docker to use a proxy. When using a BlueCoat proxy, ensure you encode the values correctly.

  1. On the machine on which you installed the engine, navigate to the d1.conf file and add the following keys.

    Key

    Value

    Description

    http_proxy

    http://<user:password@proxy-server:port#>

    For example http://user:password@proxy-server:3128

    Environment uses HTTP proxy. Special characters must be escaped.

    https_proxy

    https://user:password@proxy-server:port#

    For example, https://user:password@proxy-server:3128

    Environment uses HTTPS proxy. Special characters must be escaped.

    no_proxy

    http://<user:password@proxy-server:port#>

    For example http://user:password@proxy-server:3128

    For specific addresses, a proxy bypass will be applied. Special characters must be escaped.

  2. If the environment variables are not set, or you wish to use different settings than those specified in the environment variables, set the configuration with your specific proxy details in the d1.conf file. For example:

    {"http_proxy": "http://proxy.host.local:8080",
"https_proxy": "https://proxy.host.local:8443"
"no_proxy": "https://proxy.host.local:8020"}

  3. Save the file.

  4. On the machine where you installed the engine, navigate to the upgrade.conf file and edit the file to set https_proxy to your proxy address. For example, https_proxy="https://proxy.host.local:8443".

    Note

    In an environment with a single engine, go to /usr/local/demisto/upgrade.conf. In an environment with multiple engines, go to /usr/local/demisto/<engine-name>/upgrade.conf, replacing <engine-name> with the name of the engine.

    Note that the key is in the upgrade.conf file and must be https_proxy, even if your proxy address starts with http://.

  5. Save the file.