Re: Security issue when running packages from SQL Agent.

From: Dan Guzman (guzmanda_at_nospam-online.sbcglobal.net)
Date: 09/01/04

  • Next message: Jay_Reborn: "Customer Passwords in SQL Server"
    Date: Tue, 31 Aug 2004 20:36:08 -0500
    
    

    As Kevin said, only sysadmin role members can execute CmdExec steps by
    default. Cross-database chaining is relevant only if you are executing
    xp_cmdshell from a stored procedure in a user database.

    You can allow non-sysadmin role member to execute CmdExec steps by
    unchecking the 'only users with sysadmin privileges ...' check box in
    Enterprise Manager under Management --> SQL Server Agemt --> Properties -->
    Job System. You will then be prompted to specify a valid Windows account
    for the SQL Server Agent proxy.

    The main security consideration is that non-sysadmin users are limited only
    by the Windows permissions of the proxy account. You'll need to ensure the
    account has only the rights needed to perform the needed tasks, such as
    creating files in a specific folder and limited SQL Server permissions (if
    the account has been granted access to SQL Server).

    -- 
    Hope this helps.
    Dan Guzman
    SQL Server MVP
    "GR" <anonymous@discussions.microsoft.com> wrote in message 
    news:38e501c48f85$450a45e0$a501280a@phx.gbl...
    >I am trying to execute a DTSRUN command from SQL Server
    > Agent for a user that does not have sysadmin rights.  Here
    > is the message I receive when I view the job history for
    > this job:
    >
    > "Non-SysAdmins have been denied permission to run CmdExec
    > job steps.  The step failed."
    >
    > I've heard that Cross-database ownership chaining can be
    > used to address this issue but I'm not sure how to
    > implement this logic, or how vunerable it makes your
    > server.
    >
    > Any hope would be appreciated.
    >
    > Thank you
    >
    > Gordon Radley
    >
    > 
    

  • Next message: Jay_Reborn: "Customer Passwords in SQL Server"

    Relevant Pages

    • Re: Move or Setup of SQL Database toa Remote Server Fails
      ... as well as have SysAdmin privileges on the DB. ... Registered type 501ST MASTER for 501ST SCCM1DB\master ... Could not connect SQL Server 'master' db. ... The SCCM Primary Site Computer Account and the User account I am using ...
      (microsoft.public.sms.setup)
    • Re: The Microsoft Search service cannot be administered under the pres
      ... the BUILTIN\Administrator account as well as a member of the Sysadmin role? ... SQL Server Full-Text Search Does Not Populate Catalogs ... you or your server's sysadmin have removed the ... exec sp_defaultdb N'NT Authority\System', N'master' ...
      (microsoft.public.sqlserver.fulltext)
    • Re: Schedule a DTS package
      ... It does not mean you will avoid all the security problems. ... owned by a sysadmin then the job will fire as the Service account. ... Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) ...
      (microsoft.public.sqlserver.dts)
    • Re: Schedule a DTS package
      ... Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) ... www.SQLDTS.com - The site for all your DTS needs. ... >> owned by a sysadmin then the job will fire as the Service account. ...
      (microsoft.public.sqlserver.dts)
    • Re: remove guest user in msdb
      ... in your your opinion while is the best security choice? ... Assing the sysadmin role to an NT normal user account and use this to start the SQL_SERVER_AGENT. ... > Wayne Snyder, MCDBA, SQL Server MVP ...
      (microsoft.public.sqlserver.server)