Are data-privacy regulations and dreams about stolen employee data keeping you up at night? With the Health Insurance Portability and Accountability Act (HIPAA) now a reality, though, the stakes are higher than ever when it comes to compromised customer and employee data, and many organizations are taking a second look at encrypting their databases.<\/p>\n","protected":false},"excerpt":{"rendered":"
It may be time to protect your data where it lives–in your database.<\/p>\n
But you can’t encrypt everything in your database. Indexed fields, for example, can’t be encrypted because your database-management software will sort the encrypted strings in hexadecimal values, which won’t match the real, unencrypted form. So your index, which is supposed to speed access to the data by preordering it, won’t work. Even if you could relate the encrypted index field to the original data, the collation order wouldn’t match.<\/p>\n
Until databases support encryption natively, encrypted indices will be a problem. Remember that any indices generated from encrypted fields won’t be valid, either. And because these fields don’t relate to the actual data, it’ll be harder for the database administrator and developer to debug problems. <\/p>\n
Database software, such as Sybase’s, lets you create encrypted databases.<\/p>\n
Ingrian Networks’ DataSecure Platform, which lets you encrypt certain fields before you enter them in the database and automatically decrypts them on the way out, has been around for a couple of years.<\/p>\n
Bottom line: When building your disk capacity for database encryption, anticipate that your data will triple or quadruple in size.<\/p>\n
More info: [url=http:\/\/www.securitypipeline.com\/story\/showArticle.jhtml?articleID=16600160]http:\/\/www.securitypipeline.com\/story\/showArticle.jhtml?articleID=16600160[\/url]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-31","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/31","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=31"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/31\/revisions"}],"predecessor-version":[{"id":2518,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/31\/revisions\/2518"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=31"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=31"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=31"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}