{"id":2031,"date":"2003-12-17T00:00:00","date_gmt":"2003-12-17T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2003\/12\/17\/security-event-management-projected-to-hit-430-million-by-2008\/"},"modified":"2021-12-30T11:40:31","modified_gmt":"2021-12-30T11:40:31","slug":"security-event-management-projected-to-hit-430-million-by-2008","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2003\/12\/17\/security-event-management-projected-to-hit-430-million-by-2008\/","title":{"rendered":"Security Event Management Projected To Hit $430 Million By 2008"},"content":{"rendered":"<p>The Security Event Management (SEM) market is on the rise and could grow to $430 million by 2008, according to a Yankee Group report released this week.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The $90 million SEM market could also could witness as much as 50 percent market consolidation in 2004.<br \/>\nThe report, &#8220;Security Event Management Systems Defend Against Information and Regulatory Overload,&#8221; said that as security becomes a greater concern for network administrators, SEM systems that enable them to identify, manage and respond to virus and hacker threats are becoming more prevalent.<\/p>\n<p>The $90 million SEM market also could witness as much as 50 percent market consolidation in 2004, said report author Phebe Waterfield.  &#8220;Integrating a systems management solution with risk management has the potential to revolutionize the way enterprises manage security risks,&#8221; Waterfield added.<\/p>\n<p>SEM systems burst onto the scene in the late 1990s, when security vendors created them to help network administrators cope with information overload generated by security devices.<\/p>\n<p>More info: [url=http:\/\/www.securitypipeline.com\/news\/showArticle.jhtml;jsessionid=13LHM1WGIKYFKQSNDBGCKHY?articleId=17000228]http:\/\/www.securitypipeline.com\/news\/showArticle.jhtml;jsessionid=13LHM1WGIKYFKQSNDBGCKHY?articleId=17000228[\/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-2031","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\/2031","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=2031"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2031\/revisions"}],"predecessor-version":[{"id":4518,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2031\/revisions\/4518"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=2031"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=2031"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=2031"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}