{"id":6949,"date":"2014-04-21T20:52:10","date_gmt":"2014-04-22T03:52:10","guid":{"rendered":"http:\/\/www.infosecurity.pro\/?p=6949"},"modified":"2019-04-20T16:24:35","modified_gmt":"2019-04-20T16:24:35","slug":"breach-of-2-5m-at-maricopa-county-community-college-district","status":"publish","type":"post","link":"https:\/\/www.infosecurity.pro\/?p=6949","title":{"rendered":"Breach of 2.5M at Maricopa County Community College District"},"content":{"rendered":"<p>\t\t\t\t<![CDATA[Maricopa County Community College District (MCCCD)\u00a0has 2 skill centers and 10 community colleges in Maricopa County which employ over 9500 and have approximately 265,000 current students.\u00a0 A class action claim has been made in state court which points out that the district waited over 7 months to inform the 2.5 million past and present students that their\u00a0databases of\u00a0PII had become for sale online after a breach.\nThe claim is that the FBI warned the district in January 2011 of the database breach and online sales of information.\u00a0 The district's IT employees repeatedly reported their findings to the Vice Chancellor but failure to make changes to secure the databases resulted in another breach of 14 MCCCD database servers in April 2013.\u00a0 Of the 2.5 million past and present students, employees, and vendors, the breach included their names, addresses, phone numbers, email addresses, SSNs, DOB, financial\/bank info, education, financial aid info, etc.\n\n&nbsp;\n&nbsp;]]>\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":"3","amazon-product-excerpt-hook-override":"3","amazon-product-singular-only":"","amazon-product-amazon-desc":"","amazon-product-show-gallery":"","amazon-product-show-features":"","amazon-product-newwindow":"2","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],"tags":[],"class_list":["post-6949","post","type-post","status-publish","format-standard","hentry","category-breaches","category-practices"],"_links":{"self":[{"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=\/wp\/v2\/posts\/6949","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=6949"}],"version-history":[{"count":1,"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=\/wp\/v2\/posts\/6949\/revisions"}],"predecessor-version":[{"id":7951,"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=\/wp\/v2\/posts\/6949\/revisions\/7951"}],"wp:attachment":[{"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=6949"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=6949"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=6949"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}