SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Security - when "EncryptSensitiveWithUserKey" does the user have to be the developer?


Security - when "EncryptSensitiveWithUserKey" does the user have to be the developer?

Author
Message
winston Smith
winston Smith
SSCarpal Tunnel
SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)

Group: General Forum Members
Points: 4235 Visits: 2071
We have a package with sensitive data so encryptWithUserKey, and then run in the SQL Agent using a proxy is the best option.

But, we want to use a specific proxy account,and dont want to create a proxy for the developers account.

Is it possible to set what account the package uses to EncryptWithUserKey?
Elliott Whitlow
Elliott Whitlow
SSC-Insane
SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)

Group: General Forum Members
Points: 23936 Visits: 5314
winston Smith (7/5/2013)
We have a package with sensitive data so encryptWithUserKey, and then run in the SQL Agent using a proxy is the best option.

But, we want to use a specific proxy account,and dont want to create a proxy for the developers account.

Is it possible to set what account the package uses to EncryptWithUserKey?

I would tend to use something other than EncryptSensitiveWithUserKey. I would probably more likely use EncryptSensitiveWithPassword or EncryptAllWithPassword. In general I try not to store ANYTHING sensitive in the package itself. This means that even if the EncryptSensitiveWithUserKey is set it won't actually do anything.

I would not want to have a developers account as a proxy. The effect of that would be to potentially give the developer elevated rights to production resources.

As far as whether you can tell what account was used to save the package I'm not sure you can KNOW but you might be able to see the creator name in the package properties. But that is the creator, NOT the last saved..

CEWII
winston Smith
winston Smith
SSCarpal Tunnel
SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)

Group: General Forum Members
Points: 4235 Visits: 2071
I appreciate it might not be the best solution from your point of view, but forgetting if its good or bad, is the only way to assign a new owner to the package to open and save it under the proxy account credentials? its quite a bit of hassle to do that. would be much better if you could "encryptWithSpecifiedUserKey"

Thanks for the prompt response!
Elliott Whitlow
Elliott Whitlow
SSC-Insane
SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)

Group: General Forum Members
Points: 23936 Visits: 5314
winston Smith (7/5/2013)
I appreciate it might not be the best solution from your point of view, but forgetting if its good or bad, is the only way to assign a new owner to the package to open and save it under the proxy account credentials? its quite a bit of hassle to do that. would be much better if you could "encryptWithSpecifiedUserKey"

Thanks for the prompt response!

Yes, you have to open it as the correct user, fix the credentials that are now invalid, and then re-save. That's about it..

Honestly I would change the protection level and use a password which can then be stored in the job that runs it.. YMMV

CEWII
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search