{"id":2218,"date":"2008-12-12T00:00:00","date_gmt":"2008-12-12T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2008\/12\/12\/bit9-identifies-the-dirty-dozen-2008s-most-popular-applications-with-critical-security-vulnerab\/"},"modified":"2021-12-30T11:40:53","modified_gmt":"2021-12-30T11:40:53","slug":"bit9-identifies-the-dirty-dozen-2008s-most-popular-applications-with-critical-security-vulnerab","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2008\/12\/12\/bit9-identifies-the-dirty-dozen-2008s-most-popular-applications-with-critical-security-vulnerab\/","title":{"rendered":"Bit9 Identifies &#8216;The Dirty Dozen&#8217; &#8211; 2008&#8217;s Most Popular Applications With Critical Security Vulnerab"},"content":{"rendered":"<p>Bit9, Inc., the pioneer and leader in Enterprise Application Whitelisting, unveiled its annual ranking of popular consumer applications with known security vulnerabilities.  Often running outside of the IT department&#8217;s knowledge or control, these applications can be difficult to detect; they create data leakage risk in endpoints that are otherwise secure; and cause compliance breaches that can result in costly fines.  The list this year expanded to include 12 applications, up from 10 last year, due to the increase in vulnerabilities and the popularity of applications such as Skype and Yahoo!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Each application on the list has the following characteristics: Runs on Microsoft Windows.  Relies on the end user, rather than a central IT administrator, to manually patch or upgrade the software to eliminate the vulnerability, if such a patch exists.<\/p>\n<p>To read the full list of applications, which includes products from Symantec, Yahoo!, Trend Micro, Sun Microsystems and more, visit here (http:\/\/bit9.com\/landing\/2008vulnerableapps.php) to download the research note.<\/p>\n<p>http:\/\/www.darkreading.com\/security\/app-security\/showArticle.jhtml;jsessionid=W4TNO0P1S4NS2QSNDLRSKH0CJUNN2JVN?articleID=212400451<\/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-2218","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\/2218","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=2218"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2218\/revisions"}],"predecessor-version":[{"id":4705,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2218\/revisions\/4705"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=2218"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=2218"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=2218"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}