Before we begin… Please submit any viruses for the test at http://virus.untangle.com/
Background - who we are Untangle provides an open source network gateway platform. We are not an antivirus company We are not a testing company
Background - why we are doing this 2005: Untangle researches antivirus to add to the network gateway platform after testing we choose clam (open source) and one other vendor 2006: Untangle seeks Testing Labs for certification (stickers!) 2006: Testing Lab refused to test AV product, because use of open source won’t tell us why won’t provide test results won’t provide test set Something fishy is going on here…
What is the AV FightClub? A simple test of real-world anti-virus detection by different AV engines What AV FightClub is not: Zero-day test Functionality comparison Not coverage testing Open - for samples & participation & discussion Transparent - simple, verify & run at home Two important things!
The Test Small Set of test viruses (eicar) Set of ‘in-the-wild’ viruses Set of user-submitted viruses (minus non-viruses, not ‘in-the-wild’ viruses, and phish) Each vendor is subjected to: Scored by % of viruses identified and performance if applicable All vendors should catch all these viruses
The Vendors Engines with linux support (clam, kasperskey, fprot, sophos, globalhauri) Gateway Appliances (sonicwall, fortinet, watchguard) Windows solutions (norton/symance, mcafee) Vendors
Conclusions Open Source solution (Clam) doesn’t suck. In fact, its excellent! Many vendors are poor. Some are selling dead donkeys! outstanding questions conclusions Why hasn’t this been pointed out? Is there something wrong with the way we test antivirus today?
Thanks for coming! Dirk Morris firstname.lastname@example.org Remember Contact Don’t believe me? Try this at home. The test set will be available on http://virus.untangle.comhttp://virus.untangle.com (password on zip file is “a”)