View Full Version : Sasser response times
VikingStorm
May 7th, 2004, 06:52 AM
http://www.pcwelt.de/news/viren_bugs/39734/2.html
Looks like NOD32 is excluded again?
Paul Wilders
May 7th, 2004, 07:09 AM
{QUOTE-> http://www.pcwelt.de/news/viren_bugs/39734/2.html
Looks like NOD32 is excluded again? <-QUOTE}
Looks like it; NOD32 databased Sasser.A May 1th 2004.
regards,
paul
Technodrome
May 7th, 2004, 10:32 AM
Command AV detects A variant on May 1st and B and C on May 2nd. There could be a difference in time zone and dates though…
http://www.authentium.com/threats/analysis/VirusDetail.asp?RefNo=665
NOD32 detect B variant on May 1st and C on May 2nd.
tECHNODROME
kdcdq
May 8th, 2004, 09:45 PM
OK, I feel compelled to add my $.02 worth of opinions right NOW:
1) As Technodrome pointed out previously in this thread, I don't think that the times/dates posted on the PC-Welt site are exact, BUT, they don't have to be; what IS important (to me, anyway) is the "relative order" of the products in website's vendor response table.
2) IMHO, the "relative order" of the AV products listed can be used to build a short-list of worthy AV products that can/will protect your critical computing systems. As an example, I typically run Dr. Web as my primary AV with it's on-demand scanning active; I run F-Prot, Extendia (AVK and RAV scanning engines), and Command AV as my backup/second-opinion scanners. After seeing the PC-Welt website data, I feel pretty darn good (i.e. safe) right now.
3) The commercial "main-stream buy-it-off-the-shelf" AV products (by such vendors as Symantec, Trend Micro, and McAfee) should be ashamed of themselves for taking WAY TOO LONG to post updates to detect/fix the Sasser virus, and this is not the first time (Wilder regulars: please back me up here) that they have responded poorly to address other global virus infections.
4) Congratulations to Bitdefender for being the first AV vendor to respond to the Sasser virus and for beating the other products by a potentially critical thirty minutes.
5) If any of your computers were infected by the Sasser virus even though you have/use an on-access AV product with current updates, maybe it's time to switch to a potentially better AV product. A major oil company (five letters - starts with "S") was severely hit by the Sasser virus to a degree that I cannot address in this forum; it was not a pretty sight.
6) If at all possible, stay current with security fixes to your computer's software products via Windows Update, and consider using its "auto-update" feature; I do. I use and recommend the free version of BigFix (www.bigfix.com); it's not bad and the price is right.
7) NO current AV product will catch 100% of virus infections 100% of the time. If you believe otherwise, I will sell you the Golden Gate Bridge for $1 plus some odd change.
8) Use layers of security products including firewalls, anti-virus, anti-trojan, and anti-spyware components; keep them updated. Bill Gates, the richest man in the world, once said that "PCs will be like toasters; you will just plug them in and they will make toast". I have a dream......
KDCDQ, Security Freak
TheQuest
May 8th, 2004, 10:30 PM
Hi, kdcdq
{QUOTE-> Bill Gates, the richest man in the world, once said that "PCs will be like toasters; you will just plug them in and they will make toast". <-QUOTE}
TOAST be the operative word. ;D
TheQuest 8)
TREllis
May 9th, 2004, 04:41 AM
{QUOTE-> OK, I feel compelled to add my $.02 worth of opinions right NOW:
1) As Technodrome pointed out previously in this thread, I don't think that the times/dates posted on the PC-Welt site are exact, BUT, they don't have to be; what IS important (to me, anyway) is the "relative order" of the products in website's vendor response table.
2) IMHO, the "relative order" of the AV products listed can be used to build a short-list of worthy AV products that can/will protect your critical computing systems. As an example, I typically run Dr. Web as my primary AV with it's on-demand scanning active; I run F-Prot, Extendia (AVK and RAV scanning engines), and Command AV as my backup/second-opinion scanners. After seeing the PC-Welt website data, I feel pretty darn good (i.e. safe) right now.
3) The commercial "main-stream buy-it-off-the-shelf" AV products (by such vendors as Symantec, Trend Micro, and McAfee) should be ashamed of themselves for taking WAY TOO LONG to post updates to detect/fix the Sasser virus, and this is not the first time (Wilder regulars: please back me up here) that they have responded poorly to address other global virus infections.
4) Congratulations to Bitdefender for being the first AV vendor to respond to the Sasser virus and for beating the other products by a potentially critical thirty minutes.
5) If any of your computers were infected by the Sasser virus even though you have/use an on-access AV product with current updates, maybe it's time to switch to a potentially better AV product. A major oil company (five letters - starts with "S") was severely hit by the Sasser virus to a degree that I cannot address in this forum; it was not a pretty sight.
6) If at all possible, stay current with security fixes to your computer's software products via Windows Update, and consider using its "auto-update" feature; I do. I use and recommend the free version of BigFix (www.bigfix.com); it's not bad and the price is right.
7) NO current AV product will catch 100% of virus infections 100% of the time. If you believe otherwise, I will sell you the Golden Gate Bridge for $1 plus some odd change.
8) Use layers of security products including firewalls, anti-virus, anti-trojan, and anti-spyware components; keep them updated. Bill Gates, the richest man in the world, once said that "PCs will be like toasters; you will just plug them in and they will make toast". I have a dream......
KDCDQ, Security Freak <-QUOTE}
Your post is 90% misleading and meaningless!
Update times for Sasser are just more Scheiße from PCWelt!
Even if you have 20 updated anti-virus programs installed, without the Microsoft Critical Update installed, Sasser will still get you!
{QUOTE-> I have a dream...... <-QUOTE}
You sure do!
Sandish
May 9th, 2004, 05:46 AM
{QUOTE-> Looks like it; NOD32 databased Sasser.A May 1th 2004.
regards,
paul <-QUOTE}
NOD32 can´t be included in the tests cause the signature updates are only available through the NOD32 interface. The tests are made with scripts that fetch updates from public ftp/ww sites afaik. See http://www.av-test.org/down/papers/2004-02_vb_outbreak.pdf for details.
rodzilla
May 9th, 2004, 05:47 AM
>> Looks like NOD32 is excluded again?
> Looks like it; NOD32 databased Sasser.A May 1th 2004.
This was eminently predictable ... NOD32's "zero seconds" heuristic detection was deliberately omitted from an earlier "response times" article in PC-Welt ... even though the author was fully aware that NOD32 detected and blocked the virus on first sight, without needing an update.
rodzilla
May 9th, 2004, 05:49 AM
> Update times for Sasser are just more Scheiße from PCWelt!
Sounds like you're a regular reader. :)
kdcdq
May 9th, 2004, 02:38 PM
Quote TREllis: "Your post is 90% misleading and meaningless!"
My Response: Everyone is entitled to their own opinions. I must not have learned anything about computers & security during my 23 years in Computer Information Technology and/or by building/reparing/upgrading/trouble-shooting/networking PCs for the last 7 years.
Quote TREllis "Update times for Sasser are just more Scheiße from PCWelt!"
My Response: This is completely possible. I am in the process of trying to formulate my own "Sasser Response Table" like PCWelt did. When I finish, I will publish my own set of numbers with detailed explanations of exactly how the numbers were derived.
Quote TREllis: "Even if you have 20 updated anti-virus programs installed, without the Microsoft Critical Update installed, Sasser will still get you!"
My Response: This statement is partially true; 20 "bad" AV programs may not equal good security. The Microsoft Critical Update to prevent Sasser-like virus infections has long been available; I addressed this in my original post. Sasser did not "get" a lot of computers that were using updated security programs/environments.
KDCDQ, Security Freak
NOD32 user
May 15th, 2005, 02:47 PM
{QUOTE-> .... NOD32's "zero seconds" heuristic detection .... NOD32 detected and blocked the virus on first sight, without needing an update. <-QUOTE}Doesn't really matter what the virus is - "zero seconds" heuristic detection really is the main point.
Happy Bytes
May 15th, 2005, 03:13 PM
{QUOTE-> Doesn't really matter what the virus is - "zero seconds" heuristic detection really is the main point. <-QUOTE}
Did you set your system time to the correct year? :o
I mean does it show 2005 in the system try? :o
Coz you're replying here to a thread - exactly 1 year old :o
Gyuri
May 15th, 2005, 03:21 PM
;D ;D ;D pmpl
Don Pelotas
May 15th, 2005, 03:55 PM
{QUOTE-> Did you set your system time to the correct year? :o
I mean does it show 2005 in the system try? :o
Coz you're replying here to a thread - exactly 1 year old :o <-QUOTE}
;D ;D ;D
NOD32 user
May 15th, 2005, 08:56 PM
....it took me a year to find it! :D
vBulletin® Copyright ©2000-2008, Jelsoft Enterprises Ltd.