Configuring Threat Emulation on the Security Gateway - Autonomous Threat Prevention

Important -On the 3900 appliances, Threat EmulationClosed Check Point Software Blade on a Security Gateway that monitors the behavior of files in a sandbox to determine whether or not they are malicious. Acronym: TE. does not support Local Emulation (Known Limitation PMTR-115010).

Preparing for Local or Remote Emulation

Changing the Analysis Location

You can select or change the location of the emulation analysis in the Threat Emulation page in Gateway Properties.

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 action 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.

  • 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 uses the images that are selected in both places. An image that is selected only for the appliance or for the profile is not used for emulation.