Database encryption

brettski · Post by **brettski** » Thu Nov 18, 2004 11:08 pm

I noticed that you encrypt sprocs and triggers in the database for vault. I have also noticed that this encryption doesn't seem to have much of a performance hit. As database and application developer, I am curious what you are using for this encryption. Thank you in advance.

Post by **jclausius** » Fri Nov 19, 2004 9:15 am

It is mostly used to keep the stored procedures and triggers from the casual viewer. The same can be said for some of Vault's managed code.

With that said, please note all database related materials are covered by copyright and the licensing agreement for Vault.

brettski · Post by **brettski** » Mon Nov 22, 2004 7:54 am

Thank you for your reply. I am not looking for your sprocs and triggers, I am looking for the application which Sourcegear is using to encrypt this data. I am looking or data encryption in my own databases. I do and will respect all copyrights.

Post by **jclausius** » Mon Nov 22, 2004 9:01 am

The manner in which the stored procedures and triggers are encrypted are different from the data stored within the database.

If you are looking at protecting data stored within the database, take a look at subject material regardging SHA-1, MD5, Triple DES, RSA. I'd recommend finding a book from Bruce Schneier regarding the topic.

If you are wanting to prevent your stored procedures / triggers from being seen ( or replicated ) within SQL Server, take a look at SQL Server's WITH ENCRYPTION flag.