{"id":7339,"date":"2017-07-30T03:13:21","date_gmt":"2017-07-30T10:13:21","guid":{"rendered":"http:\/\/www.infosecurity.pro\/?p=7339"},"modified":"2019-04-20T16:24:11","modified_gmt":"2019-04-20T16:24:11","slug":"job-search-websites-of-16-states-exposed-ssns","status":"publish","type":"post","link":"https:\/\/www.infosecurity.pro\/?p=7339","title":{"rendered":"Job search websites of 16 states exposed SSNs"},"content":{"rendered":"<p>\t\t\t\t<![CDATA[\n\n<p>On March 12th, a breach of the Kansas Department of Commerce&#39;s &quot;America&#39;s Job Link Alliance-TS&quot; job search websites server was discovered. &nbsp; Two days later, the sites were locked down but only after 563,568 residents had their info harvested along with 1,393,109 of Alabama, 896,380 of Arizona, and 807,450 of Illinois. &nbsp;In total, 5.5 million SSNs had been leaked from Arkansas, Arizona, Delaware, Idaho, Kansas, Maine, Oklahoma, Vermont, Alabama, and Illinois.<\/p>\n\n\n\n\n<p>Kansas has no official data breach notification laws and wound up paying SHI $235,000 for &nbsp;incident response and $175,000 to Shook, Hardy, and Bacon lawyers for legal representation. &nbsp;It has been reported that only 260,000 notification emails wee sent to victims because &quot;they don&#39;t have the contact details for everyone affected.&quot;<br \/>\n&nbsp;<\/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":[66,67,64],"tags":[],"class_list":["post-7339","post","type-post","status-publish","format-standard","hentry","category-breaches","category-practices","category-risks"],"_links":{"self":[{"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=\/wp\/v2\/posts\/7339","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=7339"}],"version-history":[{"count":1,"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=\/wp\/v2\/posts\/7339\/revisions"}],"predecessor-version":[{"id":7848,"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=\/wp\/v2\/posts\/7339\/revisions\/7848"}],"wp:attachment":[{"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=7339"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=7339"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=7339"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}