Can we create Multiple threat prevention profile in R80.10 , One profile with AV & AB blade enabled with prevent action and the other profile is having only IPS enabled .
Hi Libin, yes that should be fine provided you're installing to R80.10 gateways (Pre R80 gateways need to have a dedicated IPS layer).
You can configure separate profiles / layers to match however you need to configure your policy.
Clone the Optimized profile twice, rename one clone to ABAV and another to IPSOnly, edit profiles and uncheck not needed blades. Adjust the desired protections.
Create another rule in the Threat prevention policy with edited profiles applied to desired scopes.
i am interested to understand the need for duplicate the profiles....
can you share the reason (even directly by mail)?
two examples for best practices "why you should work with all the blades"
Oren, you can use all the blades in each threat prevention profile, but limit the activated protections in each to only those applicable to protected scopes.
I.e. "Windows Servers" scope, for instance, unlikely need to be subjected to the protections for Linux, Cisco, Adobe, etc..
Similarly, Linux hosts do not need protections for IIS, SQL, etc., and only the MTAs and mail servers may need protections particular to smtp, pop3 and imap.
There are also some vendor-specific protections, (i.e. D-Link router vulnerabilities coverage), which you may not have in your environment at all.
By narrowing-down the profiles and the protections enabled in each to only those pertinent to the scope in rule, you are increasing effectiveness and reducing load on the gateways.
Vladimir - this is one of the usages and i totally agree that by working with Scope - it will be much much more effective.
i am looking for those exactly examples from our customers & partners in our community to improve our out of the box Threat Prevention profiles.
the common admin just want to protect his network and doesn't have the time or resources to use all our great features (protections TAGS as an example).
do you have any other examples for dividing the TP profiles for your network?
For the rough profiles definitions, we can use "Windows" and "Linux" specific profiles.
Under Windows profile category, Servers and Clients (with Servers, omitting the things like Adobe Flash and Reader, IE and other, application specific protections).
Under Linux, same breakdown with Server and Client (with server, omitting browser and application specific protections).
MS SQL as a separate category, since it is now could run on both, Windows and Linux.
Separate overall SQL category covering all relational databases.
Separate Mail category.
Separate Cisco category (too many vulnerabilities and easily defined scope).
Separate category for the overall protection from worms.
Separate category for CPU level exploits.
I would think that the above will cover the needs of most lazy admins:)
Would be nice to have a correlation tool capable of matching protections to the results of the vulnerability scans, such as Nessus, Qualys, Open VAS and Vulners, by comparing their csv output with protections available from CP and generating custom profiles that could be imported.
Having this capability will enable admins to immediately plug the discovered holes.
If this tool could do differential profile updates, that will be totally awesome.
Ability to merge rules with identical scope may also be handy, (i.e. rule added immediately after 0 day discovery as a separate line item that could later be integrated with one or more stable rules).
Just my 2 cents.
i think that its a great idea (import a list of relevant vulnerabilities to your network, compare to your profile and present an out-put for "which vulnerabilities should be enabled for better protection)
regard adding a new rule - we are updating the package of our blades all the time and if you will use our recommendation profile you will get it automatically - should we do something different? (basically we do not use rules for new protections - we update the TP profile in IPS case and update the cloud in AV/AB case)
Presently, when you are adding new protections to the "Basic", "Recommended" or "Optimized" profiles and those are placed into staging, there are no indicators of whether those will change state to "Protect" or "Detect", so you are forced to select one of the actions manually.
But if you are relying on "Automatic Activation according to profile settings":
You are not sure which state the new protection will be placed in.
Having explicit notification about new protections and the state they are placed in automatically integrated in Threat Prevention, would be great: else we have to look at external references, find protections individually in IPS and either either enable action or verify it manually.
if you are using staging mode, the idea is that you will decide what to do with a signature (based on your knowledge/need/limitations).
the interesting thing that you are proposing is to add a comment to the new signature we added regardless the profile status - 'what Check Point will do with it in case of optimize OR strict'.
back to the original question from Libin Thomas original post - if we could have out-of-the-box profiles for Threat Prevention, what they would be? what are the common profiles you are using in your networks and especially what are the changes you are doing in our pre-defined profiles?
Profile suggestions as per my previous post:
I typically use clones of the "Optimized" with protections irrelevant to scope disabled and those found by vulnerability scanners in scope, enabled.
Since I am consulting, each case is different.
Retrieving data ...