Creating Threat Prevention Rules

Create and manage the policy for the Threat Prevention Software Blade as part of the Threat Prevention Policy.

• The Threat Prevention page shows the rules and exceptions for the Threat Prevention policy. The rules set the Threat profiles for the network objects or locations defined as a protected scope.

Click the Add Rule button to get started.

• You can configure the Threat Prevention settings in the Threat Prevention profile for the specified rule.
• To learn about bots and protections, look through the ThreatWiki.

Best Practice - Disable a rule when you work on it. Enable the rule when you want to use it. Disabled rules do not affect the performance of the Gateway. To disable a rule, right click in the No. column of the rule and select Disable.

Configuring IPS Profile Settings

To configure IPS settings for a Threat Prevention profile:

1. In SmartConsole, select Security Policies > Threat Prevention.
2. From the Threat Tools section, click Profiles.

   The Profiles page opens.

3. Right-click the profile, and click Edit.
4. From the navigation tree, click IPS > Additional Activation.
5. Configure the customized protections for the profile.
6. From the navigation tree, click IPS > Updates.
7. Configure the settings for newly downloaded IPS protections.
8. If you import IPS profiles from a pre-R80 deployment:
   1. From the navigation tree, click IPS > Pre-R80 Settings.
   2. Activate the applicable Client and Server protections.
   3. Configure the IPS protection categories to exclude from this profile.

   Note - These categories are different from the protections in the Additional Activation page.

9. Click OK.
10. Install Policy.

Updates

There are numerous protections available in IPS. It takes time to become familiar with those that are relevant to your environment. Some are easily configured for basic security and can be safely activated automatically.

In the Threat Prevention profile, you can configure an updates policy for IPS protections that were newly updated. You can do this with the IPS > Updates page in the Profiles navigation tree. Select one of these settings for Newly Updated Protections:

• Active - According to profile settings - Selected by default. Protections are activated according to the settings in the General page of the Profile. This is the Check Point recommended configuration.

  Set activation as staging mode - Newly updated protections remain in staging mode until you change their configuration. The default action for protections in staging mode is Detect. You can change the action manually in the IPS Protections page.

  Click Configure to exclude specific protections from staging mode.

• Inactive - Newly updated protections are not activated

Best Practice - In the beginning, allow IPS to activate protections based on the IPS policy. During this time, you can analyze the alerts that IPS generates and how it handles network traffic, while you minimize the impact on the flow of traffic. Then you can manually change the protection settings to suit your needs.

Blocking Viruses

To block viruses and malware in your organization:

1. In SmartConsole, click Gateways & Servers and double-click the Security Gateway.
2. In the General Properties page, select the Anti-Virus Software Blade.

   The First Time Activation window opens.

3. Select According to the Anti-Bot and Anti-Virus policy and click OK.
4. Close the gateway Properties window and publish the changes.
5. Click Security Policies > Threat Prevention > Policy > Threat Prevention.
6. Click Add Rule.

   A new rule is added to the Threat Prevention policy. The Software Blade applies the first rule that matches the traffic.

7. Make a rule that includes these components:
   • Name - Give the rule a name such as Block Virus Activity.
   • Protected Scope - The list of network objects you want to protect. In this example, the Any network object is used.
   • Action - The Profile that contains the protection settings you want. The default profile is Optimized.
   • Track - The type of log you want to get when detecting malware on this scope. In this example, keep Log and also select Packet Capture to capture the packets of malicious activity. You will then be able to view the actual packets in SmartConsole > Logs & Monitor > Logs.
   • Install On - Keep it as All or choose specified gateways to install the rule on.
8. Install the Threat Prevention policy.

Configuring Anti-Bot Settings

Here you can configure the Anti-Bot UserCheck Settings:

• Prevent - Select the UserCheck message that opens for a Prevent action
• Ask - Select the UserCheck message that opens for an Ask action

Blocking Bots

To block bots in your organization, install this default Threat Policy rule that uses the Optimized profile, or create a new rule.

To block bots in your organization:

1. In SmartConsole, click Gateways & Servers.
2. Enable the Anti-Bot Software Blade on the Gateways that protect your organization. For each Gateway:
   1. Double-click the Gateway object.
   2. In the Gateway Properties page, select the Anti-Bot Software Blade.

      The First Time Activation window opens.

   3. Select According to the Anti-Bot and Anti-Virus policy
   4. Click OK.
3. Click Security Policies > Threat Prevention > Policy > Threat Prevention.

   You can block bots with the out-of-the-box Threat Prevention policy rule with the default Optimized Profile.

   Alternatively, add a new Threat Prevention rule:

   1. Click Add Rule.

      A new rule is added to the Threat Prevention policy. The Software Blade applies the first rule that matches the traffic.

   2. Make a rule that includes these components:
      • Name - Give the rule a name such as Block Bot Activity.
      • Protected Scope - The list of network objects you want to protect. By default, the Any network object is used.
      • Action - The Profile that contains the protection settings you want. The default profile is Optimized.
      • Track - The type of log you want to get when the gateway detects malware on this scope.
      • Install On - Keep it as Policy Targets or select Gateways to install the rule on.
4. Install the Threat Prevention policy.
   The IPS, Anti-Bot, Anti-Virus, Threat Emulation and Threat Extraction Software Blades have a dedicated Threat Prevention policy. You can install this policy separately from the policy installation of the Access Control Software Blades. Install only the Threat Prevention policy to minimize the performance impact on the Security Gateways.

   To install the Threat Prevention policy:

   1. From the Global toolbar, click Install Policy.

      The Install Policy window opens showing the installation targets (Security Gateways).

   2. Select Threat Prevention.
   3. Select Install Mode:
      • Install on each selected gateway independently - Install the policy on the selected Security Gateways without reference to the other targets. A failure to install on one Security Gateway does not affect policy installation on other gateways.

        If the gateway is a member of a cluster, install the policy on all the members. The Security Management Server makes sure that it can install the policy on all the members before it installs the policy on one of them. If the policy cannot be installed on one of the members, policy installation fails for all of them.

      • Install on all selected gateways, if it fails do not install on gateways of the same version - Install the policy on all installation targets. If the policy fails to install on one of the Security Gateways, the policy is not installed on other targets of the same version.
   4. Click OK.

Monitoring Bot Activity

Scenario: I want to monitor bot activity in my organization without blocking traffic at all. How can I do this?

In this example, you will create this Threat Prevention rule, and install the Threat Prevention policy:

To monitor all bot activity:

1. In SmartConsole, select Security Policies > Threat Prevention.
2. Create a new profile:
   1. From the Threat Tools section, click Profiles.

      The Profiles page opens.

   2. Right-click a profile and select Clone.
   3. Give the profile a name such as Monitoring_Profile.
   4. Edit the profile, and under Activation Mode, configure all confidence level settings to Detect.
   5. Select the Performance Impact - for example, Medium or lower.

   This profile detects protections that are identified as an attack with low, medium or high confidence and have a medium or lower performance impact.

3. Create a new rule:
   1. Click Threat Prevention > Policy > Threat Prevention.
   2. Add a rule to the Rule Base.

      The first rule that matches is applied.

   3. Make a rule that includes these components:
      • Name - Give the rule a name such as Monitor Bot Activity.
      • Protected Scope - Keep Any so the rule applies to all traffic in the organization.
      • Action - Right-click in this cell and select Monitoring_Profile.
      • Track - Keep Log.
      • Install On - Keep it as Policy Targets or choose Gateways to install the rule on.
4. Install the Threat Prevention policy.
   The IPS, Anti-Bot, Anti-Virus, Threat Emulation and Threat Extraction Software Blades have a dedicated Threat Prevention policy. You can install this policy separately from the policy installation of the Access Control Software Blades. Install only the Threat Prevention policy to minimize the performance impact on the Security Gateways.

   To install the Threat Prevention policy:

   1. From the Global toolbar, click Install Policy.

      The Install Policy window opens showing the installation targets (Security Gateways).

   2. Select Threat Prevention.
   3. Select Install Mode:
      • Install on each selected gateway independently - Install the policy on the selected Security Gateways without reference to the other targets. A failure to install on one Security Gateway does not affect policy installation on other gateways.

        If the gateway is a member of a cluster, install the policy on all the members. The Security Management Server makes sure that it can install the policy on all the members before it installs the policy on one of them. If the policy cannot be installed on one of the members, policy installation fails for all of them.

      • Install on all selected gateways, if it fails do not install on gateways of the same version - Install the policy on all installation targets. If the policy fails to install on one of the Security Gateways, the policy is not installed on other targets of the same version.
   4. Click OK.

Disabling a Protection on One Server

Scenario: The protection Backdoor.Win32.Agent.AH blocks malware on windows servers. How can I change this protection to detect for one server only?

In this example, create this Threat Prevention rule, and install the Threat Prevention policy:

To add an exception to a rule:

1. In SmartConsole, click Threat Prevention > Policy > Layer.
2. Click the rule that contains the scope of Server_1.
3. Click the Add Exception toolbar button to add the exception to the rule. The gateway applies the first exception matched.
4. Right-click the rule and select New Exception.
5. Configure these settings:
   • Name - Give the exception a name such as Exclude.
   • Protected Scope - Change it to Server_1 so that it applies to all detections on the server.
   • Protection/Site - Click + in the cell. From the drop-down menu, click the category and select one or more of the items to exclude.

     Note - To add EICAR files as exceptions, you must add them as Whitelist Files. When you add EICAR files through Exceptions in Policy rules, the gateway still blocks them, if archive scanning is enabled.

   • Action - Keep it as Detect.
   • Track - Keep it as Log.
   • Install On - Keep it as Policy Targets or select specified gateways to install the rule on.
6. Install Policy.

Configuring Threat Emulation Settings

Before you define the scope for Threat Prevention, you must make sure that your DMZ interfaces are configured correctly. To do this:

1. In SmartConsole, click Gateways & Servers and double-click the Security Gateway.

   The gateway window opens and shows the General Properties page.

2. From the navigation tree, click Network Management and then double-click a DMZ interface.
3. In the General page of the Interface window, click Modify.
4. In the Topology Settings window, click Override and Interface leads to DMZ.
5. Click OK and close the gateway window.

Do this procedure for each interface that goes to the DMZ.

If there is a conflict between the Threat Emulation settings in the profile and for the Security Gateway, the profile settings are used.

To configure Threat Emulation settings for a Threat Prevention profile:

1. In SmartConsole, select Security Policies > Threat Prevention.
2. From the Threat Tools section, click Profiles.

   The Profiles page opens.

3. Right-click the profile, and click Edit.
4. From the navigation tree, go to Threat Emulation and configure these settings:
   1. General Threat Emulation Settings.
   2. Emulation Environment
   3. Advanced Threat Emulation Settings.
5. Click OK and close the Threat Prevention profile window.
6. Install the Threat Prevention policy.

Selecting the Threat Emulation Action

What are the available emulation actions that I can use with a Threat Emulation profile?

• Prevent - Files do not go to the destination computer until emulation is completed. If Threat Emulation discovers that a file contains malware, the malicious file does not enter the internal network. Users can notice a delay when downloading a file, because they cannot download and open the file until the emulation is complete.
• Detect - The file is sent to the destination and to Threat Emulation. If Threat Emulation discovers that a file contains malware, the appropriate log action is done. Users receive all files without delay.

  Note - To estimate the system requirements and amount of file emulations for a network, go to sk93598.

Emulation Environment

You can use the Emulation Environment window to configure the emulation location and images that are used for this profile:

• The Analysis Locations section lets you select where the emulation is done
  • Check Point ThreatCloud - Files are sent to the Check Point ThreatCloud for emulation. The emulation in the ThreatCloud is identical to a local emulation but it does not use CPU, RAM, and disk space on a local appliance. When you configure ThreatCloud emulation, a secure SSL connection is created between the company's Security Gateway and the ThreatCloud. Files are sent to the ThreatCloud over this secure connection for emulation. The results are sent back to the Security Gateway and the applicable action is done to the file.
  • Local Threat Emulation appliance - The Emulation appliance that does the emulation and file analysis. Threat Emulation uses the CPU, RAM and disk space of the appliance to do the emulation.
  • Other Threat Emulation appliance - Enable Threat Emulation on a Security Gateway and select the Emulation appliance that does the emulation.
  • To use the Security Gateway settings for the location of the virtual environment, click According to the gateway.
  • To configure the profile to use a different location of the virtual environment, click Specify and select the applicable option.

    Note - In the Remote Emulation Appliances option, for R80.10 gateways with R80.10 Jumbo Hotfix Accumulator and R77.20 gateways, you can select multiple appliances for remote emulation. For older gateways, you can select only one appliance for remote emulation.

• The Environments section lets you select the operating system images on which the emulation is run. If the images defined in the profile and the Security Gateway or Emulation appliance are different, the profile settings are used.

  These are the options to select the emulation images:

  • To use the emulation environments recommended by Check Point security analysts, click Use Check Point recommended emulation environments
  • To select other images for emulation, that are closest to the operating systems for the computers in your organization, click Use the following emulation environments

Excluding Emails

You can enter email addresses that are not included in the Threat Emulation protection. SMTP traffic that is sent to or from these addresses is not sent for emulation.

Note - If you want to do emulation on outgoing emails, make sure that you set the Protected Scope to Inspect incoming and outgoing files.

To exclude emails from the Threat Emulation protection:

1. From the Threat Prevention profile navigation tree, go to the Mail tab > Exceptions > Emulation Exceptions.
2. Click Configure.
3. In the Recipients section, you can click the Add button and enter one or more emails.

   Emails and attachments that are sent to these addresses will not be sent for emulation.

4. In the Senders section, you can click the Add button and enter one or more emails.

   Emails and attachments that are received from these addresses will not be sent for emulation.

   Note - You can also use a wildcard character to exclude more than one email address from a domain.

5. Click OK and close the Threat Prevention profile window.
6. Install the Threat Prevention policy.

Preparing for Local or Remote Emulation

Prepare the network and Emulation appliance for a Local or Remote deployment in the internal network.

1. Open SmartConsole.
2. Create the network object for the Emulation appliance.
3. If you are running emulation on HTTPS traffic, configure the settings for HTTPS Inspection.
4. Make sure that the traffic is sent to the appliance according to the deployment:
   • Local Emulation - The Emulation appliance receives the traffic. The appliance can be configured for traffic the same as a Security Gateway.
   • Remote Emulation - The traffic is routed to the Emulation appliance.

Using Local or Remote Emulation

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

Note - Prepare the network for the Emulation appliance before you run the First Time Configuration Wizard.

To enable an Emulation appliance for Local and Remote emulation:

1. In SmartConsole, go to Gateways & Servers and double-click the Emulation appliance.

   The Gateway Properties window opens.

2. From the Network Security 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.
4. Click Next.

   The Summary page opens.

5. Click Finish to enable Threat Emulation on the 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 Emulation appliance.

To enable Threat Emulation on the Security Gateway for Remote emulation:

1. In SmartConsole, go to Gateways & Servers and double-click the Security Gateway.

   The Gateway Properties window opens.

2. From the Network Security tab, select Threat Emulation.

   The Threat Emulation First Time Configuration Wizard opens and shows the Emulation Location page.

3. Configure the Security Gateway for Remote Emulation:
   1. Select Other Threat Emulation appliances.
   2. Click Next.
   3. Click the + sign to add the emulation appliances. For R80.10 gateways with R80.10 Jumbo Hotfix Accumulator and R77.20 gateways, you can add multiple appliances for remote emulation. For older gateways, you can select only one remote emulation appliance.
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 Emulation appliance.

Configuring Threat Extraction Settings

To configure Threat Extraction settings for a Threat Prevention profile:

1. In the Security Policies view > Threat Tools section, click Profiles.
2. Right-click a profile and select Edit.

   The Profiles properties window opens.

3. On the General Policy page in the Blade Activation area, select Threat Extraction.
4. Configure these Threat Extraction Settings:
   • General
   • Advanced.
5. Click OK.

Note - You can configure some of the Threat Extraction features in a configuration file, in addition to the CLI and GUI. See sk114613.

Configuring Threat Extraction on the Security Gateway

To configure the Threat Extraction blade on the gateway:

1. Enable the Threat Extraction Blade:
   1. On the General Properties > Network Security tab, select Threat Extraction.

      The Threat Extraction First Time Activation Wizard opens.

   2. Optional: If you want Threat Extraction to scan email attachments, you must enable the MTA and configure the Domain and Next Hop.

      If you do not want Threat Extraction to scan email attachments, click Skip this configuration now.

   3. Click Next.
   4. Click Finish.
2. In the Gateways & Servers view, open the gateway properties > Threat Extraction page.
3. Make sure the Activation Mode is set to Active.
4. In the Resource Allocation section, configure the resource settings.
5. Click OK.
6. Install the Access Control Policy.

In addition to configuring Threat Extraction on the gateway, enable Threat Extraction to scan one or all of these types of documents:

• For Threat Extraction to scan e-mail attachments, Enable the gateway as a Mail Transfer Agent (MTA).
• For Threat Extraction to scan web downloads, in SmartConsole, go to the Security Policies view > Threat Prevention > Threat Tools > Profiles > double-click a profile > Threat Extraction > General > Protocol, and select Web (HTTP/HTTPS).
• For Threat Extraction API support, in the gateway editor, go to Threat Extraction > Web API > Enable API.

Configuring a Malware DNS Trap

The Malware DNS trap works by configuring the Security Gateway to return a false (bogus) IP address for known malicious hosts and domains. You can use the Security Gateways external IP address as the DNS trap address but:

• Do not use a gateway address that leads to the internal network
• Do not use the gateway internal management address
• If the gateway external IP address is also the management address, select a different address for the DNS trap.

You can also add internal DNS servers to better identify the origin of malicious DNS requests.

Using the Malware DNS Trap you can detect compromised clients by checking logs with connection attempts to the false IP address.

At the Security Gateway level, you can configure the DNS Trap according to the profile settings or as a specific IP address for all profiles on the specific gateway.

To set the Malware DNS Trap parameters for the profile:

1. In SmartConsole, select Security Policies > Threat Prevention.
2. From the Threat Tools section, click Profiles.

   The Profiles page opens.

3. Right-click the profile, and click Edit.
4. From the navigation tree, click Malware DNS Trap.
5. Click Activate DNS Trap.
6. Enter the IP address for the DNS trap.
7. Optional: Add Internal DNS Servers to identify the origin of malicious DNS requests.
8. Click OK and close the Threat Prevention profile window.
9. Install the Threat Prevention policy.

To set the Malware DNS Trap parameters for a gateway:

1. In SmartConsole, click Gateways & Servers and double-click the Security Gateway.

   The gateway window opens and shows the General Properties page.

2. From the navigation tree, select Anti-Bot and Anti-Virus.
3. In the Malicious DNS Trap section, select one of these options:
   • According to profile settings - Use the Malware DNS Trap IP address configured for each profile.
   • IPv4 - Enter an IP address to be used in all the profiles assigned to this Security Gateway.
4. Click OK.
5. Install the policy.

Exception Rules

If necessary, you can add an exception directly to a rule. An exception sets a different Action to an object in the Protected Scope from the Action specified Threat Prevention rule. In general, exceptions are designed to give you the option to reduce the level of enforcement of a specific protection and not to increase it. For example: The Research and Development (R&D) network protections are included in a profile with the Prevent action. You can define an exception which sets the specific R&D network to Detect. For some Anti-Bot and IPS signatures only, you can define exceptions which are stricter than the profile action.

You can add one or more exceptions to a rule. The exception is added as a shaded row below the rule in the Rule Base. It is identified in the No. column with the rule's number plus the letter E and a digit that represents the exception number. For example, if you add two exceptions to rule number 1, two lines will be added and show in the Rule Base as E-1.1 and E-1.2.

You can use exception groups to group exceptions that you want to use in more than one rule. See the Exceptions Groups Pane.

You can expand or collapse the rule exceptions by clicking on the minus or plus sign next to the rule number in the No. column.

To add an exception to a rule:

1. In the Policy pane, select the rule to which you want to add an exception.
2. Click Add Exception.
3. Select the Above, Below, or Bottom option according to where you want to place the exception.
4. Enter values for the columns. Including these:
   • Protected Scope - Change it to reflect the relevant objects.
   • Protection - Click the plus sign in the cell to open the Protections viewer. Select the protection(s) and click OK.
5. Install Policy.

Note - You cannot set an exception rule to an inactive protection or an inactive blade.

Blade Exceptions

You can also configure an exception for an entire blade.

To configure a blade exception:

1. In the Policy, select the Layer rule to which you want to add an exception.
2. Click Add Exception.
3. Select the Above, Below, or Bottom option according to where you want to place the exception.
4. In the Protection/Site column, select Blades from the drop-down menu.
5. Select the blade you want to exclude.
6. Install Policy.