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

Step |
Instructions |
---|---|
1 |
In SmartConsole, go to Gateways & Servers and double-click the Security Gateway object of the Threat Emulation appliance. The Gateway Properties window opens. |
2 |
From the Threat Prevention tab, select SandBlast Threat Emulation. The Threat Emulation First Time Configuration Wizard opens and shows the Emulation Location page. |
3 |
Select Locally on a Threat Prevention device. shouldn't it be-locally on this appliance? |
4 |
Click Next. The Summary page opens. |
5 |
Click Finish to enable Threat Emulation on the Threat Emulation appliance and close the First Time Configuration Wizard. |
6 |
Click OK. The Gateway Properties window closes. |
7 |
For Local emulation, install the Threat Prevention policy on the Threat Emulation appliance. |

Step |
Instructions |
---|---|
1 |
In SmartConsole, go to Gateways & Servers and double-click the Security Gateway object. The Gateway Properties window opens. |
2 |
From the Threat Prevention tab, select SandBlast Threat Emulation. The Threat Emulation First Time Configuration Wizard opens and shows the Emulation Location page. |
3 |
Configure the Security Gateway for Remote Emulation:
|
4 |
Click Next. The Summary page opens. |
5 |
Click Finish to enable Threat Emulation on the Security Gateway close the First Time Configuration Wizard. |
6 |
Click OK. The Gateway Properties window closes. |
7 |
Install the Threat Prevention policy on the Security Gateway and the Threat Emulation appliance. |
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).

Step |
Instructions |
---|---|
1 |
Double-click the Security Gateway object of the Threat Emulation appliance. The Gateway Properties window opens. |
2 |
From the navigation tree, select Threat Emulation. The Threat Emulation page opens. |
3 |
![]()
|
4 |
![]() Select Emulate files on ThreatCloud if not supported locally. If files are not supported on the Threat Emulation appliance and they are supported in the ThreatCloud, they are sent to the ThreatCloud for emulation. No additional license is necessary for these files. |
5 |
Click OK. |
6 |
Install the policy on the Threat Emulation appliance. |
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 Prevent 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 Detect
UserCheck rule action that allows traffic and files to enter the internal network and logs them. and log malware.

Step |
Instructions |
---|---|
1 |
Double-click the Security Gateway object of the Threat Emulation appliance. |
2 |
From the navigation tree, select Threat Emulation. The Threat Emulation page opens. |
3 |
From the Activation Mode section, select one of these options:
|
4 |
Click OK, and then install the policy. |
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.

Step |
Instructions |
---|---|
1 |
Double-click the Security Gateway object of the Threat Emulation appliance. The Gateway Properties window opens. |
2 |
From the navigation tree, select Threat Emulation > Advanced. The Advanced page opens. |
3 |
Stopping the emulation is determined when the Log storage mechanism automatically deletes log files. Therefore, in order to change the relevant configured value (Note - It also affects the Log's files deletion). Navigate to Logs > Local Storage >. And from When disk space is below |
4 |
To configure the maximum amount of RAM that is available for emulation, select Limit memory allocation. |
5 |
![]()
|
6 |
![]() Select the action if a file is not sent for emulation:
|
7 |
Click OK, and then install the policy. |
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.

Step |
Instructions |
---|---|
1 |
Double-click the Security Gateway object of the Threat Emulation appliance. The Gateway Properties window opens. |
2 |
From the navigation tree, select Threat Emulation > Advanced. |
3 |
From the Image Management section, select the applicable option for your network:
|
4 |
Click OK, and then install the policy. |