Installing the DSG

Installing the DSG On-Premise

The Data Security Gateway (DSG) installation requires an existing ESA. It serves as a single point of management for the data security policy, rules configuration, and on-going monitoring of the system. This section provides information about the recommended order of the steps to install a DSG appliance.

Before you begin

• Ensure that an ESA v10.1.x is installed.

  For more information about installing the ESA v10.1.x, refer to the sections Installing Appliance On-Premise and Installing Appliances on Cloud Platforms.

• Ensure that HubController service is running on the ESA.

• Ensure that Policy Management (PIM) has been initialized on the ESA. The initialization of PIM ensures that cryptographic keys for protecting data and the policy repository have been created.
  For more information about initializing the PIM, refer to section Initializing the Policy Management.

• Ensure that the FIPS mode is disabled on the ESA.
  For more information about diabling the FIPS mode, refer to the section Disabling the FIPS Mode

• Ensure that Analytics component is initialized on the ESA. The initialization of Analytics component is required for displaying the Audit Store information on Audit Store Dashboards.
  For more information about initializing Analytics, refer Initializing Analytics on the ESA.

• Ensure that the list of patches are available for DSG 3.3.0.1 release. The following table describes the patch details.

  Patch	Description
  ESA_PAP-ALL-64_x86-64_10.1.0.xxxx.DSGUP.3.3.0.1.x.pty	This patch is applied on the ESA to extend the ESA with the DSG Web UI.
  DSG_PAP-ALL-64_x86-64_3.3.0.1.x.iso	The .iso image is used to install the DSG appliance.

Installation Order

To setup the DSG, it is recommended to use the following installation order.

Note: By default, the default_80 HTTP tunnel is disabled for the security reasons. If you want to use default_80 HTTP tunnel in any service, then you must enable the default_80 HTTP tunnel from the Web UI.
To enable the default_80 HTTP tunnel, on the ESA Web UI, navigate to Cloud Gateway > 3.3.0.1 {build number} > Transport. Then, click the Tunnels tab. Select the default_80 HTTP tunnel and click Edit.
After the default_80 tunnel is enabled, you must restart the gateway. On the Tunnels tab, click Deploy to All Nodes to restart the gateway.