{"id":2008,"date":"2003-11-06T00:00:00","date_gmt":"2003-11-06T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2003\/11\/06\/conqueror-worm\/"},"modified":"2021-12-30T11:40:27","modified_gmt":"2021-12-30T11:40:27","slug":"conqueror-worm","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2003\/11\/06\/conqueror-worm\/","title":{"rendered":"Conqueror Worm?"},"content":{"rendered":"<p>The rapid appearance of variants of the just-detected MiMail.C mass-mailer worm makes it clear that the timeline for IT-security response is getting ever shorter.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Last week&#8217;s elevated warning levels surrounding MiMail.C, a new, fast-spreading worm, gave IT departments time to brace themselves for a new round of attacks&#8211;but only barely.<\/p>\n<p>The arrival of this new family of worms is not without attendant irony: MiMail.C arrived just as SoBig finally lost its spot at the top of the &#8220;Most Popular Virus&#8221; heap.<\/p>\n<p>MiMail may or may not achieve a similar &#8220;status,&#8221; but the time between first deployment and release of refined versions spanned just a couple of months.<\/p>\n<p>But those vendors&#8211;and all IT security professionals, for that matter&#8211;face an ongoing challenge of shortening the time between detection, alert announcement, and effective prevention and\/or removal tools.<\/p>\n<p>More info: [url=http:\/\/www.securitypipeline.com\/showArticle.jhtml;jsessionid=Z2SCZM2ERD0ASQSNDBGCKHY?articleId=16000158]http:\/\/www.securitypipeline.com\/showArticle.jhtml;jsessionid=Z2SCZM2ERD0ASQSNDBGCKHY?articleId=16000158[\/url]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11],"tags":[],"class_list":["post-2008","post","type-post","status-publish","format-standard","hentry","category-trends"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2008","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=2008"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2008\/revisions"}],"predecessor-version":[{"id":4495,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2008\/revisions\/4495"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=2008"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=2008"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=2008"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}