Configuring Advanced Threat Emulation Settings - Autonomous Threat Prevention

Updating Threat Emulation

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. connects to the ThreatCloudClosed The cyber intelligence center of all of Check Point products. Dynamically updated based on an innovative global network of threat sensors and invites organizations to share threat data and collaborate in the fight against modern malware. to update the engine and the operating system images. The default setting for the Threat Emulation appliance is to automatically update the engine and images.

The default setting is to download the package once a day.

Best Practice - Configure Threat Emulation to download the package when there is low network activity.

Update packages for the Threat Emulation operating system images are usually more than 2GB. The actual size of the update package is related to your configuration.

Updating Threat Emulation Images Manually

Update packages for the Threat Emulation operating system images are usually more than several Gigabytes. The actual size of the update package is related to your configuration.

The default setting is to download the package once a week on Sunday. If Sunday is a work day, we recommend that you change the update setting to a non-work day.

Fine-Tuning the Threat Emulation Appliance

You can change the advanced settings on the Threat Emulation appliance to fine-tune Threat Emulation for your deployment.

Configuring the Emulation Limits

To prevent too many files that are waiting for emulation, configure these emulation limit settings:

If emulation is not done on a file for one of these reasons, the Fail Mode settings for Threat Prevention define if a file is allowed or blocked:

  • Allow all connections (Fail-open) - All connections are allowed in a situation of engine overload or failure (default).

  • Block all connections (Fail-close) - All connections are blocked in a situation of engine overload or failure.

Changing the Size of the Local Cache

When a Threat Emulation analysis finds that a file is clean, the file hash is saved in a cache. Before Threat Emulation sends a new file to emulation, it compares the new file to the cache. If there is a match, it is not necessary to send it for additional emulation. Threat Emulation uses the cache to help optimize network performance. We recommend that you do not change this setting.