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


Securing DTS connections for Sarbanes Oxley


Securing DTS connections for Sarbanes Oxley

Author
Message
cooljdude
cooljdude
SSC-Enthusiastic
SSC-Enthusiastic (106 reputation)SSC-Enthusiastic (106 reputation)SSC-Enthusiastic (106 reputation)SSC-Enthusiastic (106 reputation)SSC-Enthusiastic (106 reputation)SSC-Enthusiastic (106 reputation)SSC-Enthusiastic (106 reputation)SSC-Enthusiastic (106 reputation)

Group: General Forum Members
Points: 106 Visits: 144

Hi,

We have jobs scheduled on several of our Database Servers, which execute DTS packages. The DTS packages have Connections (steps) to more than one Sql Servers (different applications). Because of the Sarbanes Oxley requirements, we are trying to come up with a way where only the primary developer for any given application would know the password for that application/Sqlserver. And because we have integrations between different systems/applications via DTS packages, we want to come up with a scenario where the developer of the DTS package would not need to know the password for the connection step to the other application involved in the DTS.

This is what we have come up with so far:

In our Development environment, the developers will have access to all the databases on all the sql servers via their NT domain accounts. Thus, they can create the DTS packages with connections to different sql server /databases (Development only) using windows authentication on all connection steps and then test it. When the DTS needs to be deployed, only the primary developer for the production database where the DTS/Job is to be housed, will have access to do so. He/She will copy (save as) the DTS to the production server, and then schedule it as a job. The DTS owner will thus be the primary developer for the application who has sa privileges.

If my understanding is correct, when the DTS is executed by the job, if the DTS uses 'Windows authentication' on the connection steps, the credentials associated with the sql server agent log on (from the machine where the job is running), will be used for authentication. Is this correct? If it is, then if we have sql server agents on all our instances to start using a windows domain account that has administrative rights, would this approach work? It seems like the NT domain admin account falls under the BuiltIn/Administrator login. WE have that login under the Sa role.

Would this approach work? Is there any downside to using such a mechanism.

Moreover, when the credentials from the sql server agent log on are passed to authenticate against any sql database, how does sql server figure out that this log on is part of the builtin/administrator group? Does Active Directory come into play at all?

Jaladhi


Site Owners
Site Owners
SSChampion
SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)

Group: Administrators
Points: 12683 Visits: 20
No one has responded to this topic yet. Even if you don't have a complete answer, the original poster will appreciate any thoughts you have!
Mark Harr
Mark Harr
SSCrazy
SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)

Group: General Forum Members
Points: 2706 Visits: 191

If my understanding is correct, when the DTS is executed by the job, if the DTS uses 'Windows authentication' on the connection steps, the credentials associated with the sql server agent log on (from the machine where the job is running), will be used for authentication. Is this correct?

Not necessarily. It depends on the owner of the job, or the Run as user setting on the job step. If that user is in the sysadmin role, it should use the SQL Server agent account for authentication. If that user is not in the sysadmin role group, it will use the SQL Server Agent proxy account that is defined. If the proxy account is not defined, the job step will fail. See Handling Package Security in DTS in BOL for more on this.





Mark
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