You can set environment variables that apply globally across the Splunk SOAR (Cloud) runtime environment to manage proxies or other features. You can also override or provide these variables on a per-app basis in the app advanced configuration. Changes to global environment settings will not be applied until the Splunk SOAR (Cloud) platform is restarted.

To make changes to the global environment:

1. From the Splunk SOAR (Cloud) main menu, select Administration.
2. Click Administration Settings > Environment Settings.
3. Click +Variable to add a new environment variable.
4. In the Name field, specify HTTP_PROXY, HTTPS_PROXY, or NO_PROXY depending on the type of proxy connection. These environment variables are read by all Splunk SOAR (Cloud) processes and affect the entire product including external search connections, app and asset connections, and requests made from within playbooks.
   CAUTION: These variable names are case sensitive and must be entered as HTTP_PROXY, HTTPS_PROXY, or NO_PROXY.
5. In the Value field, include the following depending on the type of proxy configuration. Wildcards are not supported.
   1. HTTP and HTTPS proxy configurations: protocol, hostname or IP address, and the port of the proxy server. For example,

      <protocol>://<hostname/IP>:<port>

   2. NO_PROXY configurations: IP address, hostname, or domain of the asset.
   3. (Conditional) If the proxy server requires authentication, consider the following items:
   • <scheme>://[<username>[:<password>]@]<host>[:port]> is the scheme (http or https), optional username and password, host name or IP address, and optional port number used to connect to the proxy server.
   • The scheme and host are required.
   • If using a proxy server that requires authentication Splunk SOAR (Cloud) may need a service account on the proxy server.
   • If authentication credentials (username/password) are specified, the "secret" box should be selected so that the username and password are stored in encrypted format.
   • If port is not specified it defaults to port 80 when the scheme is http, and port 443 when the scheme is https.
6. Check Secret to encrypt the Value field and stop it from being displayed.

The global action concurrency limit designates the maximum number of concurrent actions across all assets on the Splunk SOAR (Cloud) platform.

• The default setting is 50 concurrent actions on the SOAR platform.
• Cisco Talos connector, Splunk Enterprise Security (Mission Control), and SMTP each have a concurrency limit of 50.
• The Splunk Automation Broker concurrent actions limit can be set up to the same limit as is set in Splunk SOAR (Cloud). Setting a higher limit of concurrent actions on the automation broker than in Splunk SOAR (Cloud) has no effect.

To change the local concurrent action limit in Splunk SOAR (Cloud), follow these steps.

1. From the Home menu, select Administration.
2. Click Administration Settings > Environment Settings.
3. Enter your desired action limit in the box. Use caution when changing this limit because doing so can have a significant effect on performance.
4. Click Save Changes.

To change the local concurrent action limit in the Automation Broker, follow these steps.

1. Edit brokerd.conf by either:
   • navigating to your data directory on the Docker host operating system.
   • by logging into the Automation Broker container to edit the file in the /broker directory.
   See Change Splunk SOAR Automation Broker settings by editing brokerd.conf in Set Up and Manage the Splunk SOAR Automation Broker.
2. Set the value for global_concurrency_limit to the desired value.
3. Save and exit the file.
4. Restart the Automation Broker. See Interact with the Splunk Automation Broker in Set Up and Manage the Splunk SOAR Automation Broker.