I'm wanting to encrypt my SQL Server 2012 database and it looks like TDE encryption is the best fit for me. Step 1 is to create a database master key for the master database, and it seems I don't have the permissions to do this. There must be a way to encrypt a database on DASP, perhaps via a different method? Can anyone provide any information here? Thanks, Jennifer
We do not support TDE because it essentially encrypt the database file rather than the data. What exactly are you trying to do? Do you want to encryption a column of sensitive data?
I'll have a table containing personal information of 'customers of my customers'. That's the most likely place of concern. It's not going to be anything as sensitive as a credit card number, but some of my customers have policies requiring the encryption of any personal data relating to their customers. Since the need/extent of the encryption will vary across my customers, ideally I'd like the solution to be something that has a fairly light-weight impact on the front-end web application - so that if I have one customer who wants 16 different columns encrypted, and others who want none encrypted, or everything in between, I don't have to make massive changes to the front-end for each customer. I had looked at various SQL Server options, but given the options you support, what approach would you recommend? Thanks, Jennifer
Looks like you just want to encrypt a column then. this should be helpful http://msdn.microsoft.com/en-us/library/ms179331.aspx
Frank why is that the TDE is not supported. It does encrypt database file but that is a very important aspect of database security. Specially, as database backups are stored in a file system on hosting environment.
TDE is only supported in Enterprise edition of SQL. The Service Provider license cost for Enterprise edition is significantly more than standard / web edition. If we were to offer Enterprise edition, we'll have to drastically increase the cost for MS SQL.
That makes sense. Do you provide Enterprise edition hosting as well? It would be good option to have. I do not mind paying more for security.
We do not. If there was sufficient demand it could be something that we considered for future implementation, but honestly I haven't seen many people asking for Enterprise SQL Server features.
