Facebook-Icon
Twitter-Icon
False Alarm Tests
With AV testing it is important to measure not only detection capabilities but also reliability - one of reliability aspects is certainly product's tendency to flag clean files as infected. No product is immune from false positives (FP’s) but there are differences among them and the goal is to measure them. Nobody has all legitimate files that exist and so no "ultimate" test of FP’s can be done.
 
What can be done and is reasonable, is to create and use a set of clean files which is independent. If on such set one product has e.g. 50 FP’s and another only 10, it is likely that the first product is more prone to FP’s than the other. It doesn't mean the product with 10 FP’s doesn't have more than 10 FP’s globally, but important is the relative number.
 
In order to better evaluate the quality of the detection capabilities of anti-virus products, we provide also a false alarm test. False alarms can sometimes cause as much troubles as a real infection. Please consider the false alarm rate when looking at the detection rates, as a product which is prone to cause false alarms achieves higher scores easier. All discovered false alarms were reported and sent to the respective Anti-Virus vendors and have now been already fixed.
 
The below reports are appendix reports of the file detection tests.
 
Title Date Report (PDF)

False Alarm Test

March 2012

Report (English)

False Alarm Test

August 2011

Report (English)

False Alarm Test

February 2011

Report (English)
Report (Chinese)
False Alarm Test August 2010 Report (English)
False Alarm Test February 2010 Report (English)
False Alarm Test August 2009 Report (English)


Older detailed FP reports can be found inside the on-demand test reports (February 2009 and prior).

 
Banner