SQL Server Column Encryption

By: Jeremy Kadlec   |   Updated: 2006-06-09   |   Comments (3)   |   Related: > Encryption

Problem

When the most valuable component in your environment is storing sensitive data, doing so in clear text and relying on other security mechanisms to protect the data has come and gone. As companies begin to use SQL Server for all their mission critical applications, data encryption has becomes a feature that is often needed to protect the data. Moreover, legislation and growing security concerns have brought data security to the forefront of many IT shops things to do list.

Solution

Unfortunately, SQL Server 2000 has no native capabilities to encrypt a column. Companies use a third party product to meet this need. Here are some products on the market:

• NetLib Encryptionizer for SQL Server
• SQL Server encryption with XP_CRYPT

• Master key
• Certificate
• Symmetric key
• Apply the encryption key to the column

Next Steps

• Work with your business and legal teams to understand which data needs to be protected and how it is currently being protected. Ask the question - 'Are these security measures acceptable?' and see if column level encryption is necessary.
• Determine other portions of your data that require encryption such as communications, file systems, files, backups, etc.
• Take some time to review and test these technologies to determine if they are suitable for your needs.
• Work with your team to rollout this level of security to properly protect your data.

About the author

Jeremy Kadlec is a Co-Founder, Editor and Author at MSSQLTips.com with more than 300 contributions. He is also the CTO @ Edgewood Solutions and a six-time SQL Server MVP. Jeremy brings 20+ years of SQL Server DBA and Developer experience to the community after earning a bachelor's degree from SSU and master's from UMBC.

This author pledges the content of this article is based on professional experience and not AI generated.

View all my tips