Configuring Threat Emulation on the Security Gateway

Preparing for Local or Remote Emulation

Using Local or Remote Emulation

This section is for deployments that use a Threat Emulation appliance and run emulation in the internal network.

Note - Prepare the network for the Threat Emulation appliance before you run the First Time Configuration Wizard (see The Threat Emulation Solution).

Changing the Analysis Location

When you run the Threat Emulation First Time Configuration Wizard, you select the location of the emulation analysis. You can use the Threat Emulation window in Gateway Properties to change the location.

Note - The Threat Prevention policy defines the analysis location that is used for emulation (see Emulation Environment).

Setting the Activation Mode

You can change the Threat Emulation protection Activation Mode of the Security Gateway or Threat Emulation appliance. The emulation can use the PreventClosed UserCheck rule action that blocks traffic and files and can show a UserCheck message. action that is defined in the Threat Prevention policy or only DetectClosed UserCheck rule action that allows traffic and files to enter the internal network and logs them. and log malware.

Optimizing System Resources

The Resource Allocation settings are only for deployments that use a Threat Emulation appliance. Threat Emulation uses system resources for emulation to identify malware and suspicious behavior. You can use the Resource Allocation settings to configure how much of the Threat Emulation appliance resources are used for emulation. When you change these settings, it can affect the network and emulation performance.

You can configure the settings for these system resources:

  • Minimum available hard disk space (If no emulation is done on a file, the Threat Prevention Fail Mode settings determine if the file is allowed or blocked (see Fail Mode).

  • Maximum available RAM that can be used for Virtual Machines.

If you plan to change the available RAM, these are the recommended settings:

  • If the appliance is only used for Threat Emulation, increase the available RAM.

  • If the appliance is also used for other Software Blades, decrease the available RAM.

Managing Images for Emulation

You can define the operating system images that Threat Emulation uses, for each appliance, and for each Threat Emulation profile. If different images are defined for a profile and for an appliance, Threat Emulation will use the images that are selected in both places. An image that is selected only for the appliance or for the profile will not be used for emulation.