{"id":916,"date":"2010-03-02T00:00:00","date_gmt":"2010-03-02T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2010\/03\/02\/verizon-offers-up-its-data-breach-framework\/"},"modified":"2021-12-30T11:38:23","modified_gmt":"2021-12-30T11:38:23","slug":"verizon-offers-up-its-data-breach-framework","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/?p=916","title":{"rendered":"Verizon Offers Up Its Data Breach Framework"},"content":{"rendered":"<p>Verizon Business here today released to the public its framework for gathering and analyzing forensics data from a data breach that is the basis for its comprehensive annual data breach reports.   The hope is that the framework will facilitate more cooperation and data-sharing among breach victim organizations.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>&#8220;When our investigators are conducting a forensics investigation, they use this tool to collect, aggregate, analyze, and report&#8230; It becomes our data breach investigation report,&#8221; says Wade Baker, director of risk intelligence for Verizon Business.<\/p>\n<p>Aside from offering a common format for reporting and sharing that data, the hope is that such a framework will facilitate and help organizations share breach information so investigators can find common threads among attacks and attackers, for instance.<\/p>\n<p>VerIS &#8212; which is available today via a free download &#8212; can be used to supplement an organization&#8217;s existing methods for collecting attack data and analysis, or as a replacement.<\/p>\n<p>Verizon&#8217;s Baker says half of all incidents his firm has investigated during the past couple of years have been related in some way.<\/p>\n<p>http:\/\/www.darkreading.com\/insiderthreat\/security\/attacks\/showArticle.jhtml?articleID=223100886&#038;cid=RSSfeed<\/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-916","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/916","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=916"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/916\/revisions"}],"predecessor-version":[{"id":3403,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/916\/revisions\/3403"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=916"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=916"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=916"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}