{"id":29029,"date":"2015-02-06T00:44:17","date_gmt":"2015-02-06T05:44:17","guid":{"rendered":"http:\/\/www.opensource.im\/uncategorized\/why-even-strong-crypto-wouldnt-protect-ssns-exposed-in-anthem-breach.php"},"modified":"2015-02-06T00:44:17","modified_gmt":"2015-02-06T05:44:17","slug":"why-even-strong-crypto-wouldnt-protect-ssns-exposed-in-anthem-breach","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/cryptography\/why-even-strong-crypto-wouldnt-protect-ssns-exposed-in-anthem-breach.php","title":{"rendered":"Why even strong crypto wouldn\u2019t protect SSNs exposed in Anthem breach"},"content":{"rendered":"<p><p>Steven M. Bellovin is a professor in the computer science    department at Columbia University. This post was originally    published on his blog. This    essay quickly generated a vigorous    debate among security experts on Twitter.      <\/p>\n<p>    Another day,     another data breach, and another round of calls for    companies to encrypt their databases. Cryptography is a    powerful tool, but in cases like this, it's not going to help.    If your OS is secure, you don't need the crypto; if it's not,    the crypto won't protect your data.  <\/p>\n<p>    In a case like the Anthem breach, the really sensitive    databases are always in use. This means that they're    effectively decrypted: the database management systems (DBMS)    are operating on cleartext, which means that the decryption key    is present in RAM somewhere. It may be in the OS, it may be in    the DBMS, or it may even be in the application itself (though    that's less likely if a large relational database is in use,    which it probably is). What's to stop an attacker from    obtaining that key, or perhaps from just making database    queries?  <\/p>\n<p>    The answer, in theory, is other forms of access control.    Perhaps the DBMS requires authentication, or operating system    permissions will prevent the attacker from getting at the keys.    Unfortunatelyand as these many data breaches showthese    defenses are not configured properly or aren't doing the job.    If that's the case, though, adding encryption isn't going to    help; the attacker will just go around the crypto. There's a    very simple rule of thumb here:Encryption is most    useful when OS protections cannot work.  <\/p>\n<p>    What do I mean by that? The most obvious situation is where the    attacker has physical access to the device. Laptop disks should    always be encrypted; ditto flash drives, backup media, etc.    Using full disk encryption on your servers' drives isn't a bad    idea, since it protects your data when you discard the media,    but you then have to worry about where the key comes from if    the server crashes and reboots.  <\/p>\n<p>    Cloud storage is a good place for encryption, since you don't    control the machine room and you don't control the hypervisor.    Again, your own operating system isn't blocking a line of    attack. (Note: I'm not saying that the cloud is a bad idea; if    nothing else, most cloud sysadmins are better at securing their    systems than are folks at average small companies.) E-mail is    another good use for encryption, unless you control your own    mail servers. Why? Because the data is yours, but you're    storing it on someone else's computer.  <\/p>\n<p>    Encryption is a useful tool (and a fun research area), but like    all tools, it's only useful if properly employed. If used in    inappropriate situations, it won't provide protection and will    create operational headaches and perhaps data loss from    mismanaged keys.  <\/p>\n<p>    Protecting large databases like Anthem's is a challenge. We    need better software security, and we need better structural    tools to isolate the really sensitive data from average, poorly    protected machines. There may even be a role for encryption,    but simply encrypting the social security numbers isn't going    to do much.  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>Original post:<br \/>\n<a target=\"_blank\" href=\"http:\/\/arstechnica.com\/security\/2015\/02\/why-even-strong-crypto-wouldnt-protect-ssns-exposed-in-anthem-breach\" title=\"Why even strong crypto wouldn\u2019t protect SSNs exposed in Anthem breach\">Why even strong crypto wouldn\u2019t protect SSNs exposed in Anthem breach<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> Steven M. Bellovin is a professor in the computer science department at Columbia University. This post was originally published on his blog<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1600],"tags":[],"class_list":["post-29029","post","type-post","status-publish","format-standard","hentry","category-cryptography"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/29029"}],"collection":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/comments?post=29029"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/29029\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=29029"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=29029"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=29029"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}