Connect agents behind a proxy

To protect computers that require a proxy to access the Internet, Deep Security Manager, or relays, you need to configure Deep Security Manager with the proxy's address. It will give this information to agents. (Alternatively, you can use the CLI to configure proxy settings locally on the agent.)

In this topic:

Requirements

Deep Security Agent 10.0 or later (not GA) is required if connecting agents to a relay or manager via proxy (especially for application control rulesets).

Register the proxy in Deep Security Manager

  1. In Deep Security Manager, go to Administration > System Settings > Proxies.
  2. In the Proxy Servers area, create a new HTTP proxy by clicking New in the menu bar.
  3. Enter the protocol, IP Address, port number, user name and password.

Connect agents, appliances, and relays to security updates via proxy

Alternatively, you can use the command line to configure proxy use instead.

  1. Still on the Proxies tab, in the Proxy Server Use area, change the Primary Security Update Proxy used by Agents, Appliances, and Relays setting to point to the new proxy.
  2. Click Save.

Connect agents to security services via proxy

  1. On Deep Security Manager, go to Policies.
  2. Double-click to edit the policy that you use to protect computers that are behind the proxy.
  3. Go to Anti-Malware > Smart Protection.
  4. In the Smart Protection Server for File Reputation Service section, Default (if it's the policy named "Base Policy") or Inherited.
  5. Select When accessing Global Smart Protection service, use proxy, then select the name of the proxy.
  6. Click Save.
  7. Go to Web Reputation > Smart Protection.
  8. In the Smart Protection Server for Web Reputation Service section, deselect the Default (if it's the policy named "Base Policy") or Inherited.
  9. Select When accessing Global Smart Protection service, use proxy, then select the name of the proxy.
  10. Click Save.
  11. Go to the Advanced tab.
  12. In the Ports section, select a group of port number that includes your proxy's listening port number, and then click Save.

    For example, if you’re using a Squid proxy server, you would select the Port List Squid Web Server. If you don’t see an appropriate group of port numbers, go to Policies > Common Objects > Lists > Port Lists and then click New.

Connect agents to a relay via proxy

  1. In the top right-hand corner of Deep Security Manager, click Support > Deployment Scripts.
  2. From Proxy to contact Relay(s), select a proxy.
  3. Copy the script or save it.
  4. Run the script on the computer. You can either do this manually or with a third party deployment system such as Ansible, Chef, Powershell, or others.

Connect agents to a relay's private IP address

If your relay has an elastic IP address, agents within an AWS VPC may not be able to reach the relay via that IP address. Instead, they must use the private IP address of the relay group.

  1. Go to Administration > System Settings.
  2. In the System Settings area, click the Updates tab.
  3. Under Software Updates, in the window Alternate software update distribution server(s) to replace Deep Security Relays , type:

    https://<IP>:<port>/

    where <IP> is the private network IP address of the relay, and <port> is the relay port number

  4. Click Add.
  5. Click Save.
If your relay group’s private IP changes, you must manually update this setting. It will not be updated automatically.

Remove a proxy setting

If you've installed an agent with a deployment script that adds proxy settings that you no longer require, you can remove the setting by entering the following commands in a command line:

Windows

>C:\Program Files\Trend Micro\Deep Security\dsa_control -x ""

C:\Program Files\Trend Micro\Deep Security\dsa_control -y ""

Linux

/opt/ds_agent/dsa_control -x ""

/opt/ds_agent/dsa_control -y ""

Subsequent agent deployments

After your initial deployment, if you add more agents, modify their deployment scripts to use the proxy in the Deployment Scripts Generator.