Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / General / Security / July 2006

Tip: Looking for answers? Try searching our database.

Service account Standards

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Greg Larsen - 27 Jul 2006 16:15 GMT
I'm trying to finalize my service account standards for SQL Server 2000 and
2005.   Here is what I have.  Does anyone have comments on these standards:



Standards for setting up SQL Server service accounts:

·        Set up a different domain account for each service if network
resources are needed.  If no network resources are needed then a local
account should be set up for those services that no not need network
resource.  Justification: This allows rights to be assigned differently
depending on the service.  Also allows for better audit trail of determine
where commands are coming from.  Also minimizes security risks by only
allowing network resources to those services that need them.

·        Give each domain account only the network permissions they require.
Justification: Minimize security risks.  Service accounts only need the
necessary permissions to perform the actions required for the service.  Any
additional permission opens the door for a service to gain access to
resources they should have.

·        Each domain account should be set up with a password that never
expires, although DBA’s should develop procedures that periodically change
the passwords for these service accounts.  Justification:  You don’t want
service accounts to stop working because a password expired.  But you do want
to periodically change the password to minimize security risks associated
with never changing passwords.

·        Do not place the domain account of a service into the local
Administrators group.  Justification: Minimizes security risks.  Giving a
service account local Admin rights increase the risk of someone exploiting
the service account to gain access and/or grant permissions to machine
resources without authorization.

·        Do not place a service account into a local group, or domain group.
Justification: Minimizes security risks.  Placing a service account into a
group implies that two services would have the same rights.  The idea of
having separate accounts for each service is so rights can be assigned
specifically to what a service needs.  Placing a service account into a group
would defeat the goal of having specific right for a given service.

·        Revoke ”interactive login” permission for each services account.
Justification:  This will keep people from using this account to login into
server.  If you need to login with the service account for setup purposes
(such as to set up the Outlook Client) then these right should only be grant
temporarily while you are doing the setup.

Signature

If you are looking for SQL Server examples check out my Website at
http://www.geocities.com/sqlserverexamples

Arnie Rowland - 27 Jul 2006 16:53 GMT
Looks good.

Noticed one possible typo. Second paragraph. Should last sentence be "they
should NOT have"

Signature

Arnie Rowland, Ph.D.
Westwood Consulting, Inc

Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous

> I'm trying to finalize my service account standards for SQL Server 2000
> and
[quoted text clipped - 49 lines]
> grant
> temporarily while you are doing the setup.
Greg Larsen - 27 Jul 2006 17:06 GMT
Thanks for the review.  Good catch on the typo.
Signature

If you are looking for SQL Server examples check out my Website at
http://www.geocities.com/sqlserverexamples

> I'm trying to finalize my service account standards for SQL Server 2000 and
> 2005.   Here is what I have.  Does anyone have comments on these standards:
[quoted text clipped - 42 lines]
> (such as to set up the Outlook Client) then these right should only be grant
> temporarily while you are doing the setup.
A McGuire - 28 Jul 2006 15:01 GMT
Reminder: when changing the service account, do it via the Enterprise
Manager and not the Services manager.  That will grant the service account
the necessary registry settings you speak of, but no more than that.  If a
domain account, it should be a Domain User.  Domain accounts are only needed
to run services if you are backing up to network resources or using
clustering/replication type of configurations.

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q283811

> I'm trying to finalize my service account standards for SQL Server 2000
> and
[quoted text clipped - 49 lines]
> grant
> temporarily while you are doing the setup.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.