- 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)
Dear
FW:23500 Version:R80.10 Hotfix:R80_10_JUMBO_HF_Bundle_T56_sk11638
I have set hold mode,refer to screenshots below:
TP configuration as follow:
But the log shows as follow:
Description:
Connection was allowed because background classification mode was set. See sk74120 for more information.
"loop.sawmilliner.com" is a C2 and malware site,as follow:
I have set classification mode to hold,why still show "background classification mode was set"
Thanks!
You are looking to the wrong Software Blade. Threat Prevention is for downloads. For Site classification, you need AC and URL Filtering to be changed.
Thanks,but log match anti-virusblade.This behavior is in the DNS request phase.Can't it be blocked by tp at the DNS request stage?
Look here:
Thanks,I will try it.
Hi,
I have the same issue. I have put the URL filtering setting to Hold mode but still i am getting same logs of "It is allowed because background classification mode was set" in the logs.
Was this ever resolved? I am facing the exact same issue. Thanks.
I am also facing same issue. anyone has an idea?
I have a customer with this same issue. Does Check Point have a configuration fix for this or is this a bug?
Hello, same issue here, any news about it?
Isn't this because Checkpoint changed how DNS classification occurs? So check out:
Even though in your policy you've set Hold that will be relevant only for http, smtp, and smb. DNS will still be in background mode for optimization purposes. You'd have to manually change that in you malware_config file on the gateway if you want DNS to be in Hold mode as well.
I think what you are seeing here is normal based on the log you showed as this was a DNS query that got bypassed.
About CheckMates
Learn Check Point
Advanced Learning
WELCOME TO THE FUTURE OF CYBER SECURITY