{"id":884,"date":"2009-01-08T00:00:00","date_gmt":"2009-01-08T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2009\/01\/08\/http-www-itworld-com-security-60354-verizon-service-steps-analysis-security-risks\/"},"modified":"2021-12-30T11:38:19","modified_gmt":"2021-12-30T11:38:19","slug":"http-www-itworld-com-security-60354-verizon-service-steps-analysis-security-risks","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2009\/01\/08\/http-www-itworld-com-security-60354-verizon-service-steps-analysis-security-risks\/","title":{"rendered":"http:\/\/www.itworld.com\/security\/60354\/verizon-service-steps-analysis-security-risks"},"content":{"rendered":"<p>Verizon&#8217;s enhanced service, which begins this month, is offered at no additional cost to Verizon customers now using its risk-correlation managed security services. Verizon&#8217;s managed security services include one-time fees that start at US$1,000, plus recurring fees that start at $1,200 per month, based on number of monitored devices.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Verizon is boosting its risk-correlation analysis through use of security-event management (SEM) so it can provide a deeper level of detail about the confidentiality, integrity and availability of data in specific customer computer equipment. <\/p>\n<p>http:\/\/www.itworld.com\/security\/60354\/verizon-service-steps-analysis-security-risks<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29],"tags":[],"class_list":["post-884","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/884","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=884"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/884\/revisions"}],"predecessor-version":[{"id":3371,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/884\/revisions\/3371"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=884"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=884"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=884"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}