In This Section: |
Make a copy of the Optimized Profile before you start the initial IPS tuning. For a Multi-Domain Server deployment, we recommend that you create a separate IPS policy and perform these steps for each segment.
To clone the Optimized Profile:
A message appears and asks if you want to clone the profile.
Configure the setting of the profile to help the initial analysis of the IPS inspection with staging mode. The default action for the protections is Prevent, but staging mode protections run in Detect mode.
Configure new protections that are added to the profile to run in Prevent mode (during staging, these protections are set to Detect).
To configure the Profile:
The newly downloaded protections are set to Active – According to profile settings.
Some Firewall Inspection Settings can be configured to help protect the network. For ease of use, we included their configuration in this document.
Activate protections for the protocols that your environment uses for emails and add customized security to the mail servers.
Setting POP3/IMAP Scope
By default, when you configure the POP3/IMAP Security setting in Security policies > Inspection settings > POP3/IMAP Security, they apply to all hosts that are defined as mail servers according to the Action settings of each IPS profile. You can also limit the scope of this protection to only the specified mail servers.
To specify which hosts get the POP3/IMAP protection settings:
The Select Servers window opens and all mail servers are selected by default.
The POP3/IMAP Security inspection settings have a list of commands that IPS recognizes and inspects. The definitions of the POP3 commands apply to all IPS profiles. In the Protections Details – POP3/IMAP Security configuration window, you can edit the list of POP3 commands that apply to all profiles or edit the list of POP3 commands that apply to specific profiles.
To edit the list of POP3 commands that applies to all profiles:
To block or allow a POP3 command for a profile:
You can manage Web Intelligence to configure the Web server settings to maximize security and reduce the Security Gateway performance or the opposite.
Improving Connectivity by Setting Scope
Some inspection settings that are too severe can have a negative impact on connectivity to and from valid Web servers.
Although applying these restrictions (activating these protections) is in general good practice, they may potentially block valid sites or important applications. Applying these protections to specific Web servers can solve the connectivity problems and may enhance CPU performance. This exclusion of a Web server from a particular protection is global to all profiles.
To configure Web Protection scope:
The Check Point Host window opens, displaying the Web Server category, which is added to a host that is defined as a Web server.
You can configure connectivity-security balance for each type of Web Intelligence protection in the protection’s window, but enforcement of these configurations always depends on whether they are activated by the Web server’s IPS profile.
The IPS profile may include protections that are not necessary for your network. You can exclude these IPS protections and improve network performance. For example, if an organization does not use VoIP services, exclude the IPS protection for VoIP traffic.
Exclude Protections by Tags
Each IPS protection is classified using tags such as:
You can exclude a group of protections using the relevant tags. You can do that either as part of the profile definition or directly from the IPS Protections view.
To exclude protection by tag using IPS Protections view:
To exclude protection by tag using Threat Prevention profile definitions:
The initial performance tuning focuses on a single IPS profile that is optimized for many situations. However, we recommend you create a different policy per network segment and gateway according to the protected assets and assign different profiles to each rule in the policy.
Examples of separate profiles: