Re: SQLServerAgent Service
From: LvBohemian (LvBohemian_at_discussions.microsoft.com)
Date: 06/20/05
- Next message: Praisy: "Appdomain.CreateDomain() throws Security Exception from a Managed"
- Previous message: Olu Adedeji: "Re: Multiprotocol Encryption"
- In reply to: Olu Adedeji: "Re: SQLServerAgent Service"
- Next in thread: Mark J. McGinty: "Re: SQLServerAgent Service"
- Reply: Mark J. McGinty: "Re: SQLServerAgent Service"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sun, 19 Jun 2005 22:21:01 -0700
Thank you for replying, but as I mentioned; I am well aware that the article
states that the account used to start the SQLServerAgent Service must be a
member of the sysadmin role...
But that kind of contradicts the best practice that the account that sql
server runs under not be an administrative account...
What is the point of changing the sql service accounts if the account used
can do anything in the database?
The MSSQLServer Service does not have to be a member of the Sysadmin role
and can be a least privileged account as desirable and works fine that way...
But the SQLServerAgent Service account itself has to be a member of the
Sysadmin role in the database, and if you are using both services they both
need to be the same account...
So my point and my original question remains...
A service account that is a Sysadmin (DBA) is huge security vulnerability...
Best practice is when you want to do admin work briefly log in as an
internal sql account that has the needed privileges to do the job at hand and
log out when done and leave the sql services running as a least privileged
account...
So why am I forced to leave the sql server running under an admin account
that if exposed can be exploited?
I am looking for an alternative; which does not include running the
SQLSeverAgent Service as an admin account nor disabling it and not using the
applicable built-in features of sql server for jobs, notifications, email etc.
Thanks in advance.
- Next message: Praisy: "Appdomain.CreateDomain() throws Security Exception from a Managed"
- Previous message: Olu Adedeji: "Re: Multiprotocol Encryption"
- In reply to: Olu Adedeji: "Re: SQLServerAgent Service"
- Next in thread: Mark J. McGinty: "Re: SQLServerAgent Service"
- Reply: Mark J. McGinty: "Re: SQLServerAgent Service"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|