- Apr 13, 2013
- 3,224
I personally will just use FW Custom Mode only after initial when I want to Block those Apps that I want blocked from calling home (that's why I don't check the Create Rules For Safe Applications box in FW settings- even though they may be Safe, I may have a reason to block their access to the Network).Out of curiosity, do you always keep Firewall in Custom Ruleset or eventually change it back to Safe Mode?
Thanks.I personally will just use FW Custom Mode only after initial when I want to Block those Apps that I want blocked from calling home (that's why I don't check the Create Rules For Safe Applications box in FW settings- even though they may be Safe, I may have a reason to block their access to the Network).
Otherwise Safe Mode is optimal.
|
It's enabled but I've found it only works on Firefox. There is their own extension but not been updated for some time. Either way, browser's and dedicated extensions protect you from phishing. e.g. Smartscreen in Edge and Google Safe Browsing in Chrome/Chromium browsers and Firefox. I use uBlock Origin in Medium Mode and Necraft.I still don't understand why COMODO doesn't include a WEB protection module against phishing sites, malicious sites, sites with malware scripts etc... and I also don't understand why the detection percentage of the antivirus module is always lower than the average of other AVs .
I would keep the AV module during the installation of CIS 2025, I don't understand why only the FW is installed instead.
Block All will essentially prevent anything unknown from running (won't even get to the Sandbox). In this case there would be no need at all for VirusScope as the file attempting to be run wouldn't even get that far.Hi sister et al, what do you think about setting the containment to block all (block unknown instead of run inside the sandbox) and disabling virus scope?
Thanks sister, I only use popular software so so far, it's working ok for me. In rare occasion where something is blocked, I find Comodo reasonably fast (a few days) in verifying and whitelisting the file.Block All will essentially prevent anything unknown from running (won't even get to the Sandbox). In this case there would be no need at all for VirusScope as the file attempting to be run wouldn't even get that far.
Although doing this (Block) will certainly protect, it is, for me, far, far too restrictive.
Well, it kinda does-In settings, go to "Website Filtering", then click on "Blocked Sites". Click edit and there check both "Malware Sites" and Phishing Sites". Also you can Add other stuff like Suspicious and PUA). (note that I have no clue as to the effectiveness of this as it bores me).I still don't understand why COMODO doesn't include a WEB protection module against phishing sites, malicious sites, sites with malware scripts etc... and I also don't understand why the detection percentage of the antivirus module is always lower than the average of other AVs .
I would keep the AV module during the installation of CIS 2025, I don't understand why only the FW is installed instead.
I think the webstart is the script for the browser to be launched after uninstall completed to offer you other products or keep using it. If you've recently uninstalled a version, it's probable that it's just a temporary that can be ditched.@cruelsister: post-install sidenote: I ran NPE after CF 2025 installation setup and NPE finds a malicious or suspect script
C:\Users\vmmetoo\AppData\Local\Temp\ComodoWebStart.vbs
and suggests deleting it along with 2 related registry keys. vbs reads:
WScript.Sleep 15000
Set WshShell = CreateObject("WScript.Shell")
Call WshShell.Run("Internet Security Products From Comodo | PC Security Software", 0, False)
WshShell.RegDelete("HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run\ComodoWebStart")
Set fsObject = CreateObject("Scripting.FileSystemObject")
fsObject.DeleteFile("C:\Users\vmmetoo\AppData\Local\Temp\ComodoWebStart.vbs")
can I let NPE delete this vbs, or is it needed to properly start CF on reboot. wonder is it a run one-time script?
There are three reasons:I still don't understand why COMODO doesn't include a WEB protection module against phishing sites, malicious sites, sites with malware scripts etc
Because the product owner stated many times in the past that he is not going to invest the money or devote company resources to prioritize or improve signature detection. The only purpose of the AV module in CIS is to detect old malware and that is by intent and design as stated by the product owner. It is there as a convenience to detect old malware and newer malware is meant to be handled by virtual containment\auto-sandboxing.and I also don't understand why the detection percentage of the antivirus module is always lower than the average of other AVs .
I would keep the AV module during the installation of CIS 2025, I don't understand why only the FW is installed instead.
@cruelsister: post-install sidenote: I ran NPE after CF 2025 installation setup and NPE finds a malicious or suspect script
C:\Users\vmmetoo\AppData\Local\Temp\ComodoWebStart.vbs
and suggests deleting it along with 2 related registry keys. vbs reads:
WScript.Sleep 15000
Set WshShell = CreateObject("WScript.Shell")
Call WshShell.Run("Internet Security Products From Comodo | PC Security Software", 0, False)
WshShell.RegDelete("HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run\ComodoWebStart")
Set fsObject = CreateObject("Scripting.FileSystemObject")
fsObject.DeleteFile("C:\Users\vmmetoo\AppData\Local\Temp\ComodoWebStart.vbs")
can I let NPE delete this vbs, or is it needed to properly start CF on reboot. wonder is it a run one-time script?
COMODO... Comodo Obviously Means One Default-Deny OptionI still don't understand why COMODO doesn't include a WEB protection module against phishing sites, malicious sites, sites with malware scripts etc... and I also don't understand why the detection percentage of the antivirus module is always lower than the average of other AVs .
I would keep the AV module during the installation of CIS 2025, I don't understand why only the FW is installed instead.