Implementing Encrypted SQL Server Database Columns with .NET

Many government agencies needing HIPAA compliance, such as HUD, require encryption of certain database columns. For systems tracking victims of domestic abuse, it's critical to encrypt personally identifiable data. Fortunately, implementing encrypted database columns is simple using .NET and SQL Sever 2000.

by David Talbot

January 11, 2005

n a normal application development environment, you will likely need to use encrypted columns to store passwords if you are using a custom users table. The need for encrypted columns is even greater in the world of HIPPA compliant applications. HIPPA requires encryption of any data transmitted over public networks. Fortunately HTTPS handles that requirement quite well.

Although HIPPA doesn't explicitly require encrypted database columns, many government agencies that derive their requirements from HIPPA, such as HUD, do require encrypted columns on client-identifiable data.

It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com.
Already a member?

To become a member of DevX.com create your Member Profile by completing the form below.
Membership is free!

Already registered? Sign In

E-mail (User Name)

Create a Password

Re-enter Password

First Name

Last Name

Company

Company Size

Address

City

State/Province

Country

Postal Code/Zip

Job Function

Phone

Note: Extension number is optional, but may be included by adding an "x" before the extension number.

By registering you will also be signed up for the Enterprise Development Daily newsletter.
After registering you may choose to opt-out by clicking on the "Manage Profile" link.

Cancel