Avatar of 25112
25112

asked on 

security for sensitive package moving from dev to dba

the ssis package - when we transfer to the dba, we keep the security on the package as 'do not store key/password' option. but there is a package we are working which involves more secure details and data (financial etc).. the dba has asked to provide proper security before putting in the network drive for them to pick up..

what security do you recommend? how would you do it if you were the programmer?
Microsoft SQL Server

Avatar of undefined
Last Comment
25112
SOLUTION
Avatar of Kent Dyer
Kent Dyer
Flag of United States of America image

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Avatar of 25112
25112

ASKER

actually, kent, I am think at package level security. (encrypt this data with a password or a user key etc - (Protection Level of Packages)..
SOLUTION
Avatar of Alpesh Patel
Alpesh Patel
Flag of India image

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Avatar of Jason Yousef
Jason Yousef
Flag of United States of America image

Hi,

There're different ways and levels of security,

The most common will be "EncryptSensitiveWithPassword" or "EncryptAllWithPassword " and you can supply the password in the sql agent job, dtutel or whenever your need to run it.

Also check that link and it'll give you more information

http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/2548b905-c733-43c9-a6cc-fbfc27759d0c/

Regards,
Jason


Avatar of 25112
25112

ASKER

OK- so EncryptAllWithPassword seems like best option- we can just give the password to next person in line who needs to open and use the package/solution.

if we need to schedule this job everyday (with the EncryptAllWithPassword protection) is there going to be a problem?
Avatar of Jason Yousef
Jason Yousef
Flag of United States of America image

Nope, no problem whatever.

If the package encryption level is EncryptSensitiveWithPassword or EncryptAllWithPassword, use the Decrypt option to provide the password. If you do not inlude a password, dtexec will prompt you for the password.


from: http://msdn.microsoft.com/en-us/library/ms138023.aspx
Avatar of 25112
25112

ASKER

i could not see 'decryp' option in job properties.. is that where it is?
ASKER CERTIFIED SOLUTION
Avatar of Jason Yousef
Jason Yousef
Flag of United States of America image

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Avatar of 25112
25112

ASKER

v good - thanks all
Microsoft SQL Server
Microsoft SQL Server

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.

171K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
Ask the experts
Read over 600 more reviews

TRUSTED BY

IBM logoIntel logoMicrosoft logoUbisoft logoSAP logo
Qualcomm logoCitrix Systems logoWorkday logoErnst & Young logo
High performer badgeUsers love us badge
LinkedIn logoFacebook logoX logoInstagram logoTikTok logoYouTube logo