Kaspersky Internet Security 2011 (100%)
DrWeb Security Space 6.0 (99%)
Online Solutions Security Suite 1.5 (97%)
Outpost Security Suite Pro 2010 (97%)
Norton Internet Security 2010 (91%)
Avast! Internet Security 5.0 (91%)
Comodo Internet Security 4.1 (89%)
So is biased because Comodo did not release Comodo v5 before? jajajajajajaja so funny. Take a look to the ending date of the test, probably they started the test before Comodo v5 was released.
I’m almost sure that if they test again Comodo v5 will score the same, if comodo is really interested in fix this they should talk with Anti-Malware Test Lab to get the samples, fix the problems and make a request for another test.
Russian testing org making russian products perfect, what’s the problem? O0
I’m not that good with dates, but was CIS 5 released before october 2010?
And I would bet NIS2011 was released before october?
I will check out now
BTW maybe Norton was release 14/9 but Norton always have his product finished almost 15 days before the release date (just like microsoft does with windows) and as far as I know they offer this new version even is has not been released for testing purposes, at least they did that with AVComparatives.
I dont care if the russian av looks good or not, but according to this test Comodo can be killed/disabled by malware, that’s all I care.
I’m sure that the difference in self protection btw cis 4.1 and 5 is very little.
I don’t care how they configured, it’s the Comodo team who has to ask them what they did and how, and if really there is a problem fix it.
If I remember well a similar test was released in February this year, Comodo 4 scored with the same result they have had since february to september to fix the problem… and they problem is still there.
If that problem is till present in v5, it should be fixed.
If the problem was fixed, this thread/test is pointless.
Only a dev could answer the question, is this [bug/exploit] still present in v5?
My guess is that it is fixed. BETA was a long process and product is very stable so far, I don’t believe they would miss something like this prior to release.
If CIS V5 is vulnerable to the same attacks then it is a problem.
If Defense+ alerts were allowed during the testing and then parts of CIS were disabled then I believe this would still be a failure, right? CIS should always protect “itself” regardless of what the user does.
If I remember correctly, CIS V4 was vulnerable to scripts that were run through safe applications. In fact I believe it was MRG that used this vulnerability to uninstall CIS V4. That has been fixed in V5, so hopefully that was the source of the failure.