June 16, 2016 at 9:24 am
We are working on implementing TDE. However we have an outside entity where they have to be kept up to date via log-shipping. I understand that they will need the certificate so they can continue to receive logs. However my dilemma is that when we give them the Certificate, we will need to give them the password for the cert backup that we use internally. That diminishes, if not negates the value behind implementing TDE.
My question is that can I take two separate backups of the same certificate and give them a version of the backup of the TDE certificate that is protected with another password then the one we use internally?
Any insight is appreciated.
June 21, 2016 at 7:27 am
I agree with you, giving them the password defeats the whole concept of TDE. I would question why do they need the password? Why not your group maintain the password and only provide it when needed. Any restores (log shipping included) on the destination server should still work as long as the certificates exist.
June 21, 2016 at 7:56 am
You can take multiple backups of the certificate, with different passwords.
BUT once the certificate is restored to their server (so they can continue to receive and restore your backups,) they can then just turn around and take a backup themselves of the certificate, with a password of their choice.
As it is, they already have your data, protecting the database at-rest with TDE won't really change that. Arguably, this might be a situation to call in the lawyers to write up something to cover everyone's behinds concerning your data...
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply