{"id":1293,"date":"2004-02-23T00:00:00","date_gmt":"2004-02-23T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/02\/23\/how-long-must-you-wait-for-an-anti-virus-fix\/"},"modified":"2021-12-30T11:39:07","modified_gmt":"2021-12-30T11:39:07","slug":"how-long-must-you-wait-for-an-anti-virus-fix","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/02\/23\/how-long-must-you-wait-for-an-anti-virus-fix\/","title":{"rendered":"How Long Must You Wait for an Anti-Virus Fix?"},"content":{"rendered":"<p>Imagine that your office building was on fire, and you called the fire department, only to be told, &#8220;Please wait there while we invent a new method to fight the kind of fire you have.&#8221;  Anti-virus software can predict and prevent some never-before-seen viruses.  But all too often, a new virus can spread unchecked while software vendors develop and distribute a new &#8220;signature&#8221; file that can match the virus and kill it.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>AV-Test is not as well-known in the United States as it should be, possibly because the group is located in Germany at the Otto von Guericke University Magdeburg.  Andreas Marx, manager of <a href=\"http:\/\/www.av-test.org\/index.php3?lang=en\" title=\"AV-Test\">AV-Test<\/a>, provided test results showing how long it took 23 major anti-virus programs worldwide to come up with new signature files during the past several weeks.  The new signature files involved in the test were developed to fight four novel viruses that weren&#8217;t being caught by the preventive or &#8220;heuristic&#8221; techniques of most anti-virus programs.  These four new viruses are known as Dumaru.Y, MyDoom.A, Bagle.A and Bagle.B. <\/p>\n<p>AV-Test uses special scripts to check the servers at anti-virus companies every five minutes, looking for new signature files.<\/p>\n<p>  H:M     Anti-Virus Program<br \/>\n  06:51   Kaspersky<br \/>\n  08:21   Bitdefender<br \/>\n  08:45   Virusbuster<br \/>\n  09:08   F-Secure<br \/>\n  09:16   F-Prot<br \/>\n  09:16   RAV<br \/>\n  09:24   AntiVir<br \/>\n  10:31   Quickheal<br \/>\n  10:52   InoculateIT-CA<br \/>\n  11:30   Ikarus<br \/>\n  12:00   AVG<br \/>\n  12:17   Avast<br \/>\n  12:22   Sophos<br \/>\n  12:31   Dr. Web<br \/>\n  13:06   Trend Micro<br \/>\n  13:10   Norman<br \/>\n  13:59   Command<br \/>\n  14:04   Panda<br \/>\n  17:16   Esafe<br \/>\n  24:12   A2<br \/>\n  26:11   McAfee<br \/>\n  27:10   Symantec<br \/>\n  29:45   InoculateIT-VET <\/p>\n<p>Although new signatures are sometimes posted very quickly in special cases, many major anti-virus services schedule regular online updates only once or twice a week, AV-Test says.  Other providers, such as F-Secure, schedule updates seven times a week, while Kaspersky Labs schedules them 20 times a week, according to AV-Test&#8217;s figures.<\/p>\n<p>Kaspersky schedules new signature files the most often &#8212; and earned the fastest average response times in AV-Test&#8217;s real-time trials, shown above &#8212; because the company has a large number of people around the world analyzing viruses and developing cures, Holdsworth says.<\/p>\n<p>More info: http:\/\/itmanagement.earthweb.com\/columns\/executive_tech\/article.php\/3316511<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-1293","post","type-post","status-publish","format-standard","hentry","category-product"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1293","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=1293"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1293\/revisions"}],"predecessor-version":[{"id":3780,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1293\/revisions\/3780"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1293"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1293"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1293"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}