Welcome Guest. | Log In | Register | Membership Benefits

Five Worst Practices In Database Encryption

Poor encryption deployments risk too much critical information within databases

Oct 05, 2011 | 05:05 PM | 

By Ericka Chickowski, Contributing Editor
Dark Reading

Database encryption can add a valuable layer of security to critical data stores, but only if the encryption is done well. As the number of database encryption deployments increases, so, too, does the number of bad encryption deployments.

Following are the five most common encryption worst practices that security experts see organizations engage in today. To get the most out of their security dollars, enterprises would do well to avoid these pitfalls.

1. Storing Keys In The Wrong Place
According to some security experts, one of the worst sins of database encryption is to comingle your encryption keys with the data they're used to encrypt.

"If you’re encrypting sensitive data in your database, then one of the worst practices is to store either the key used to encrypt the data or the authentication credentials that are used to get that key in the same database as the encrypted data," says Luther Martin, chief security architect for Voltage Security. "Doing that gives you the illusion of security, but actually provides very little real security."

To really protect your data, keep the management of encryption keys separate from the database that stores the data encrypted with those keys.

2. Failing To Centralize Key Management
Many times keys end up in the wrong place -- and poorly secured, at that -- because the organization is simply too overwhelmed to keep track of them.

"One of the main issues is the sheer number of encryption keys and digital certificates in use within organizations," says Jeff Hudson, CEO of Venafi. "Research shows that it is not uncommon for an organization to be managing certificates and keys in the thousands, if not tens of thousands."

Many organizations are sold encryption, but not the means or knowledge to manage it, Hudson says.

"Encryption is only half the solution. IT departments must track where the keys are and monitor and manage who has access to them. Organizations need to quickly come to terms with how crucial encryption keys are to safeguarding the entire enterprise," he says. "This heightens the need for both a deepened understanding of encryption best practices, as well as automated key and certificate management with access controls, separation of duties, and improved polices."

Ideally, organizations should endeavor to centralize key management as much as possible in order to know what the organization has in its inventory, where keys are located, and how they're protected.

NEXT PAGE: Recipe for disaster.

1 |  2 |  Next Page » 



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dark Reading encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dark Reading moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Dark Reading further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS



Database Security Reports

report Securing The Data Warehouse
Many enterprises are building data warehouses to centralize the ever-increasing information flowing through their organizations into useful repositories. This makes good business sense, but it opens up a slew of concerns from a security standpoint. IT professionals can apply many of the same security best practices used with databases, but there are new lessons to be learned as well.

report Defend Your Data From Malicious Insiders
The biggest threat to your company?s most sensitive data may be the employee who has legitimate access to corporate databases but less-than-legitimate intentions. And while the incidence of insider data breaches has decreased, external attacks often imitate them--and do serious damage. Follow our advice to mitigate the risk.

report Ensuring Secure Database Access
Role-based access control based on least user privilege is one of the most effective ways to prevent the compromise of corporate data. But proper provisioning is a growing challenging, due to the proliferation of "big data," NoSQLdatabases, and cloud-based data storage.

Other reports from the Database Security Tech Center:

Related Content

Establishing a Strategy for Database Security is No Longer Optional
As databases continue to grow in size, complexity and importance, enterprises struggle to identify the most appropriate controls regarding their use and misuse. The report identifies best practices, including: Implementing database activity monitoring to mitigate the high levels of risk from database vulnerabilities, and address audit findings in areas such as database segregation of duties and change management; using data security measures, such as data masking and data encryption; and monitoring privileged-user access and access to critical data.

Database Activity Monitoring Is Evolving Into Database Audit and Protection
In this report, Gartner writes that "Database audit and protection (DAP) represents an evolutionary advance in database activity monitoring tools." DAP suites provide comprehensive, cross-platform support in heterogeneous database environments to protect sensitive data from inappropriate use. Organizations are increasingly concerned with optimizing database security and mitigating risks associated with database vulnerabilities.

Protecting Against Database Attacks and Insider Threats: Top 5 Scenarios
Data security presents a multi-dimensional challenge in today's complex IT environment. Multiple access paths and permission levels have resulted in a broad array of security threats and vulnerabilities. We invite you to read this new eBook: "Protecting against database attacks and insider threats" to learn the top five scenarios and essential best practices for preventing database attacks and insider threats.

Demo: Distributed Database Security with Real-time Monitoring and Audit Protection
Organizations across the globe continue to experience compromised data caused by malicious attacks, web application vulnerabilities or unauthorized changes. View this demo and learn how IBM InfoSphere Guardium? database activity monitoring can help protect your sensitive data in distributed DBMS environments with a holistic approach to data security and compliance.

Look Beyond Native Database Auditing To Improve Security, Audit Visibility, And Real-Time Protection
Today's attacks on enterprise databases are more sophisticated than ever, and they occur so fast that it's often difficult to stop them in real time. Despite significant efforts to protect enterprise databases, the number of records breached has grown each year - due to all types of internal and external attacks and violations of corporate policy.




Featured Webcasts
Featured Whitepapers
Featured Reports