There are too many such logs:
Kuaizip is a compression software,similar to WinRAR .How to inactive anti-bot detect Kuaizip.TC.gp and cancel such log.I don't think this kind of log is of any use.
However, if you insist on making your networks vulnerable for backdoors and adware, there is a way.
Open your policy, to to Threat Prevention and add exception with Anti-Bot Blade. Lookup the name of malware you want to ignore (once more, not a good idea), add it to exception and set action to Inactive.
Final warning: by doing so, you are putting your company at risk!
"Free archive software" is trying to communicate with known C&C and triggers DNS trap protection.
Are you confident there is nothing wrong here, still?
Wanted to ask the same as I did not hear anything about "Kuaizip". A quick lookup only returned malicious intends and suggestions how it can be removed. Of course my guess can be wrong here.
Valeri Loukine is right.As far as i know,kuaizip is a compression software,but when you install the software,many bundled software will be downloaded and installed,include individual virus software，these softwares are called Rogue software(流氓软件).
When we install kuaizip software,these rogue software will be install and connected to server "i.kpzip.com" to download configuration files ,then rogue software will download others "malicious software" .
Base on the above results,there are many kuaizip.TC.gp logs in smartlog.I think kuaizip shoud not connect to internet,so ，to solve this problem,I will add exception protection to prevent kuaizip.TC.gp and no log.
It just only a compression software,similar to WinRAR . I think that because this software communicate with server,So it was detected that it might be C2 behavior.
I want to exceptions this protection,how to exceptions this protection in tp blade?
You seem to miss the point. That software is already classified as adware and backdoor tool by multiple vendors. ask yourself, why free archive software communicates to Internet? How it is related to its function?
OK,I got it ,thanks very much.
I have set exception refer to your screenshot and action is prevent,as follow:
but I found that logs still show detect:
Is my configuration incorrect?
Your default action is prevent already. Also, exception rule should be ABOVE general one. I also suspect your profile is set for detect on Low Confidence.
Yes，It is detect on low confidence.But I think the protections should be prevent,because I have set exception of kuaizip.TC.gp.I think that exception rule level is higer than general one.
Retrieving data ...