Secure deployment of SSIS package
We are in the process of completing SSIS packages. However as we move
towards the deployment phase surprisingly we realized that deployment of
SSIS package is not really straight forward as terms of security.
we need to run a SSIS package using either batch file or .NET program in
production server. The caller (batch or .NET) should call the SSIS package
by supplying parameters (such as source file, destination database,
userid, password etc) and also read return code (Success/Error) from SSIS.
The user id and password should not be in clear text format visible to
anyone. We did some research and found that deployment can be done using
many options such as XML config, SQL server Configuration, environment
variables, Registry etc but did not mentioned any about password
encryption. How can we achieve security and ensure flexibility deploying
same package in multiple environment (DEV,UAT,PROD) and simple changing
the environment specific variables at the time of deployment.
I am looking for somthing where MVC/Entity framework the connection
strings are automatically encypted when the application is run first time
using following code.
Configuration config = WebConfigurationManager.OpenWebConfiguration("~");
ConfigurationSection section =
config.GetSection("connectionStrings");
if (!section.SectionInformation.IsProtected)
{
section.SectionInformation.ProtectSection("DataProtectionConfigurationProvider");
config.Save();
}
No comments:
Post a Comment