|
|
Posted by rcamarda on 04/26/06 20:45
Hello,
I have been researching the use of symmetic and asymmetic encryption in
SQL 2005 and I am pretty excited to give it a try. Through examples, I
can encrypt the data, but I cant figure out what to do next...
What I want:
1. our social security field to be encrypted so that only the person(s)
that need it can decrypt it.
2. prevent DBA's from decrypting the data themselfs
3. Simple way to encrypt the data on the table (maybe a trigger?)
I thought I would use asymmetric keys, this way I can embed the public
key into my data warehouse process to encrypt the data.
I thought I would prompt the user for the private key when the report
runs, that way I wont store the key on the server.
This would be a place to start.
Someone in the office said that we can store the keys in Active
directory, so maybe I could make this seemless to the user running the
report?
I've found a lot of great articles that got me started, but I am
needing the next step
Any Ideas would be apprecitated!
TIA
Rob
links to articles I have found handy:
http://www.databasejournal.com/features/mssql/print.php/3483931
http://www.devx.com/dbzone/Article/29232/0/page/3
http://www.sqlservercentral.com/columnists/mcoles/sql2005symmetricencryption_printversion.asp
Navigation:
[Reply to this message]
|