As long as you have image execution prevention turned on you will able to block everything. The rest is just if you allow something through and it then starts to do stuff to your system.
The Zero day test results (your 1st link) relate to CIS 3.9 and the current version is 3.13 so there have been security improvements since that test. It’s annoying that the Malware Research Group results don’t state the version of CIS tested.
At any rate, improvements are constantly being made to protect users. The Internet Security Configuration is to provide the everyday user with the best possible protection with minimal hassle to that user.
You get a lot more pop-ups with Proactive Security as much as 3 or 4 times the amount that you get with Internet Security and although it provides more protection to your system the average user who might not understand what all the pop-ups mean is going to find it confusing.
Newer versions will provide higher security with minimum fuss/pop-ups.
Don’t forget, the BoClean integration and BufferOverflow integration both enabled by default also provide further protection if your system does become infected.
Let’s hope Version 4 Beta comes out soon.
Personallly, Internet Security is enough protection for me.
Thanks for these explanation.
I’m glad to hear that Comodo is improving with each new versions being released.
Please note that I’m not saying that CIS default is not secure, because if you look at the results of the above tests, it is still one of the best.
Hopefully with the integration of a behaviour blocker in v4, usability will be enhanced and CIS will start topping in these tests like it does at Matousec.
There is a simple test that we can do for seeing the difference, CLT test.
As we can see (attached screen), most dangerous activities are also blocked in Internet Security, however to have a global protection is necessary to pass to the Proactive Security.
Firstly, I’d like to say a big thank you for your hard work on security testing software!
The reason I’m here is because there is a doubt in COMODO Forums about wich security setup is used for COMODO Internet Security tests. Is
it “internet security” or is it “proactive security”?
I do not know why you can not switch to Proactive Security; However, you could try to reinstall CIS, and after you choose “Install COMODO Firewall (Recommended)” in the next window choose “Firewall with Maximum Proactive Defence+”. This should set you up as Proactive Security. The downside is that you can not import your settings since these are set as Internet Security, so you would have to start new, sorry.
IMHO Proactive Security is the best of all just because everything is checked in CIS. I know this way CIS would pop up more, but I see it as an old professor of mine who loved to drive me crazy with questions. At the end, I was more prepared for my classes. I learned more and finally he just stopped to question me every time he could.
Now I have CIS with firewall in Custom Mode and High Alerts. Also Block All Incoming Connection stealth port to everybody. Defence+ in Paranoid mode and all checked. Image Execution in Normal with executable files to be checked.
It has been a while since I have seen a pop up alert and if I am going to install a new program just switch to Installation Mode and may be I see one or two pop up alerts at the most. So I am very please with Comodo at the moment. :comodorocks:
Thanks for that, iroc9555, I might have a go at it when I have the time.
BTW, I see that you’re using Avast 4.8; v%, although Beta, seems to be working well, although there are some threads on SSL for e-mail (I had to work around that).
I am not that brave. I will wait for the full version of Avast 5 and still wait a little.
!ot!
BTW did you reas this:
Description:
A [less critical] vulnerability has been discovered in avast! Home/Professional, which can be exploited by malicious, local users to cause a DoS (Denial of Service) or potentially gain escalated privileges.
The vulnerability is caused due to an error in aswRdr.sys when processing IOCTLs. This can be exploited to corrupt kernel memory via a specially crafted 0x80002024 IOCTL.
Successful exploitation may allow execution of arbitrary code with SYSTEM privileges.
The vulnerability is confirmed in avast! Home version 4.8.1356. Other versions may also be affected.
Solution:
Restrict local access to trusted users only.