{"id":7487,"date":"2018-08-29T06:08:41","date_gmt":"2018-08-29T13:08:41","guid":{"rendered":"http:\/\/www.infosecurity.pro\/?p=7487"},"modified":"2019-04-20T16:24:10","modified_gmt":"2019-04-20T16:24:10","slug":"quarterly-reports-of-va-missing-for-almost-9-months","status":"publish","type":"post","link":"https:\/\/www.infosecurity.pro\/?p=7487","title":{"rendered":"Quarterly reports of VA missing for almost 9 months"},"content":{"rendered":"<p>\t\t\t\t<![CDATA[\n\n<p>For nine months this year, the Department of Veterans Affairs ceased to post online quarterly <a href=\"https:\/\/www.va.gov\/about_va\/va_notices.asp\">reports<\/a> which detail information security breaches.&nbsp; These reports have been a common procedure since 2010 and was initiated as a requirement in by 2006 the Veterans Benefits, Healthcare, and Information Technology Act.&nbsp; However, Nextgov queried the department and then the 3rd quarter 2018 and 1st and 2nd quarter reports were then put online.<\/p>\n\n\n\n\n<p>The results of the quarterly reports enjoyed open transparency for many years by following them with conference calls between the VA technology chief and the press.&nbsp; This practiced ceased near the end of 2016.&nbsp;<\/p>\n\n\n\n\n<p>The 2018 reports have shown a rise from 584 in notification letters sent to veterans affected by breaches to 3,596 in the 2nd quarter.&nbsp; Congruently, the number of credit protection letters also rose from 1,059 to 1,712 in the 2nd quarter and then finally up to 2,566 in the third quarter.&nbsp; The details of cause and severity are not included in those reports.<\/p>\n\n\n]]>\t\t<\/p>\n","protected":false},"excerpt":{"rendered":"<p>\t\t\t\t<![CDATA[]]>\t\t<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"amazonpipp_noncename":"","amazon-product-isactive":"","amazon-product-single-asin":"","amazon-product-content-location":"","amazon-product-content-hook-override":"","amazon-product-excerpt-hook-override":"","amazon-product-singular-only":"","amazon-product-amazon-desc":"","amazon-product-show-gallery":"","amazon-product-show-features":"","amazon-product-newwindow":"","amazon-product-show-list-price":"","amazon-product-show-used-price":"","amazon-product-show-saved-amt":"","amazon-product-timestamp":"","amazon-product-new-title":"","amazon-product-use-cartURL":"","amazon_featured_post_meta_key":"","_amazon_featured_alt":"","amazon-product-template":"","footnotes":""},"categories":[67,64,65],"tags":[],"class_list":["post-7487","post","type-post","status-publish","format-standard","hentry","category-practices","category-risks","category-vulnerabilities"],"_links":{"self":[{"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=\/wp\/v2\/posts\/7487","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=7487"}],"version-history":[{"count":1,"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=\/wp\/v2\/posts\/7487\/revisions"}],"predecessor-version":[{"id":7812,"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=\/wp\/v2\/posts\/7487\/revisions\/7812"}],"wp:attachment":[{"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=7487"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=7487"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=7487"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}