Use Agent Initiated Communication with Cloud Accounts

In order to prevent any communication issues between the Deep Security Manager (DSM) and the Agents we recommend to use Agent Initiated Communication when activating the Agents. Also we recommend to change the communication direction to Agent/Appliance Initiated so that the Agent always start the communication instead of the DSM.

The instructions in this article show how to configure your Policy rules so that the Agents always start the communication instead of the DSM. But in addition to the Policy change you will also need to use the Agent Initiated Activation. See Unable to Resolve Instance Hostname for instruction on how to enable Agent Initiated Activation.

Create a New Policy

The easiest way to create a new Policy is to duplicate an existing one. Select any one of the policies and click the Duplicate... button.

Policies Main Tab with Duplicate button highlighted

A new window will appear. To change the communication direction between the DSM and Agent you will need to select the Settings tab on the left. Then select the Computer tab on top. You will need to change the first option in the Communication Direction section that reads "Direction of Deep Security Manager to Agent/Appliance communication as shown below.

Agent/Appliance Initiated Option in Policies Configuration

Use The New Policy

Open the Deployment Scripts window and select the new Policy from the Security Policy drop down menu as shown below.

Deployment Script Window with Agent Initiated Activation And Policy