{"id":867,"date":"2009-02-10T22:25:59","date_gmt":"2009-02-11T06:25:59","guid":{"rendered":"http:\/\/cubist.cs.washington.edu\/Security\/?p=867"},"modified":"2009-02-10T22:26:33","modified_gmt":"2009-02-11T06:26:33","slug":"current-event-%e2%80%93-faa-kaiser-permanente-security-breaches-tens-of-thousands-of-names-compromised","status":"publish","type":"post","link":"https:\/\/secblog.cs.washington.edu\/Security\/2009\/02\/10\/current-event-%e2%80%93-faa-kaiser-permanente-security-breaches-tens-of-thousands-of-names-compromised\/","title":{"rendered":"Current Event \u2013 FAA, Kaiser Permanente Security Breaches; Tens of Thousands of Names Compromised"},"content":{"rendered":"<p><img decoding=\"async\" style=\"margin: 5px; float: right; height: 200px; width: 200px;border:none\" src=\"http:\/\/www.cesac.howard.edu\/_images\/logo\/faa.jpg\" alt=\"FAA\" \/><\/p>\n<p>In another of a long line of high-profile security breaches both in and out of the government recently, the Federal Aviation Administration has announced that in the course of a breach of their computer system, over 45,000 employee names \u2013 and presumably, personal information \u2013 were compromised.  The systems were thankfully not connected to the air traffic control system or other critical operations systems.<\/p>\n<p>The FAA is said to be following up with potentially affected individuals one by one.<\/p>\n<p>Similarly, healthcare giant Kaiser Permanente reported on Sunday that nearly 30,000 employee names, addresses, Social Security numbers, and dates of birth were stolen.  The breach was a chance discovery \u2013 the files containing the data were found in the possession of one Mia Garza, who was arrested on unrelated counts of stolen property and fraud.  It is unclear how she came to possess the data, and thus it is entirely possible that copies of it are still in the hands of malicious people.  As she was arrested on December 23rd of last year, it has clearly been quite some time since the breach occurred.<\/p>\n<p>According to Kaiser, existing security policy included restricted access to sensitive information by ACL and encryption of data on electronic devices, including cell phones \u2013 both measures that sound wise.  It is still entirely possible that the issue was policy not in fact being followed \u2013 Kaiser does not know what caused to the loss of data.<\/p>\n<p>Due to the lack of detail surrounding both of these events, they serve simply as a reminder of how broadly security breaches can affect people on a personal scale.  In just a few weeks, companies and government agencies ranging from the above to RBS WorldPay \u2013 an event in which 1.5 million people&#8217;s financial information and 1.1 million Social Security numbers were stolen \u2013 Heartland Payment, which processes over four billion payments a year, and even security specialists Kaspersky have all suffered high-profile data breaches.<\/p>\n<p>Hopefully all these attacks will remind other organizations to take a long, hard look at their security systems.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In another of a long line of high-profile security breaches both in and out of the government recently, the Federal Aviation Administration has announced that in the course of a breach of their computer system, over 45,000 employee names \u2013 &hellip; <a href=\"https:\/\/secblog.cs.washington.edu\/Security\/2009\/02\/10\/current-event-%e2%80%93-faa-kaiser-permanente-security-breaches-tens-of-thousands-of-names-compromised\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":74,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-867","post","type-post","status-publish","format-standard","hentry","category-current-events"],"_links":{"self":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/867","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/users\/74"}],"replies":[{"embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/comments?post=867"}],"version-history":[{"count":2,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/867\/revisions"}],"predecessor-version":[{"id":869,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/867\/revisions\/869"}],"wp:attachment":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/media?parent=867"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/categories?post=867"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/tags?post=867"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}