- Products
- Learn
- Local User Groups
- Partners
-
More
Celebrate the New Year
With CheckMates!
Value of Security
Vendor Self-Awareness
Join Us for CPX 360
23-24 February 2021
Important certificate update to CloudGuard Controller, CME,
and Azure HA Security Gateways
How to Remediate Endpoint & VPN
Issues (in versions E81.10 or earlier)
Mobile Security
Buyer's Guide Out Now
Important! R80 and R80.10
End Of Support around the corner (May 2021)
Observed in SmartEvent that the Anti-virus is not preventing the malicious files with extension .doc, .zip etc [with severity : critical and confidence : High ], instead it is just getting detected.
I would like to know whether this is a normal behavior in hashtag#checkpoint or did i have to make any changes in my anti-virus profile configured in threat prevention blade?
Note : Threat Emulation is not enabled in this environment.
A screenshot of the log (with sensitive data masked) might be helpful.
Also curious what setting you're using for Resource Classification as shown here:
Hi Dameon
Kindly find the relevant logs regarding the issue.
Log from SmartEvent :
Engine settings :
Anti-virus Profile :
The first thing I would do is try setting the Resource Classification Mode to Hold instead of Background.
This will not allow the entire file to be sent to the endpoint until it is scanned.
Hi Dameon
I got your point. At this point we cannot set the Resource classification to Hold, as there will be an impact on traffic as it holds the files till the scanning is completed .
But the thing is, i am I able to observe some of the events with Severity High and confidence level High is getting prevented by Antivirus inspection. but the same is not happening for Critical events. Any idea on this?
And it will be really helpful if you let me know what the "inspect" option under [Threat Prevention->Profile->(Profile name)->Anti-Virus settings->Process specific file types families ] do and what will be the outcome of it?
In some cases, the file can be blocked by URL or other characteristics without transferring the entire file.
This may be why you are seeing "prevent" in some cases and "inspect" in others.
It's likely a side effect of leaving Resource Classification in Background.
If you're concerned about end users being impacted by putting Resource Classification in Hold, create a separate Threat Prevention profile just for your mail server where it set to Hold.
Create a Threat Prevention rule that refers to your email server in the Protected Scope and apply your new profile.
Mail is pretty fault-tolerant and should not be negatively impacted by this.
In the Threat Prevention profile with regard to extensions
Background classification means the file passes and classification is done afterwards.
With hold it would wait for classification and the allow/block it based on verdict.
About CheckMates
Learn Check Point
Advanced Learning
WELCOME TO THE FUTURE OF CYBER SECURITY