{"id":1360,"date":"2004-11-30T00:00:00","date_gmt":"2004-11-30T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/11\/30\/hp-to-release-virus-throttler-for-windows-in-2005\/"},"modified":"2021-12-30T11:39:14","modified_gmt":"2021-12-30T11:39:14","slug":"hp-to-release-virus-throttler-for-windows-in-2005","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/11\/30\/hp-to-release-virus-throttler-for-windows-in-2005\/","title":{"rendered":"HP to release Virus Throttler for Windows in 2005"},"content":{"rendered":"<p>Hewlett-Packard Co. is planning to build virus-throttling technology into ProLiant servers and ProCurve switches starting in early 2005, an HP executive said today.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The Virus Throttler technology is designed to slow the propagation of a virus or worm within an infected server so that administrators have time to identify the infected system and take appropriate action, said Tony Redmond, vice president and chief technology officer of HP Services.<\/p>\n<p>HP first discussed the technology at the RSA Security conference in February, but in August Redmond acknowledged that HP was having difficulty making the technology work with Microsoft Corp.&#8217;s Windows Server software.<\/p>\n<p>Any administrator who has had to disinfect a bank of afflicted PCs or servers knows how quickly viruses can spread, Redmond said.<\/p>\n<p>HP&#8217;s virus-throttling technology will help contain the spread of those viruses or worms by slowing the rate at which they multiply within a network, Redmond explained.<\/p>\n<p>http:\/\/www.computerworld.com\/securitytopics\/security\/virus\/story\/0,10801,97940,00.html<\/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-1360","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\/1360","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=1360"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1360\/revisions"}],"predecessor-version":[{"id":3847,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1360\/revisions\/3847"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1360"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1360"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1360"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}