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


Isolating services


Isolating services

Author
Message
paulaalkz 9229
paulaalkz 9229
SSC Journeyman
SSC Journeyman (78 reputation)SSC Journeyman (78 reputation)SSC Journeyman (78 reputation)SSC Journeyman (78 reputation)SSC Journeyman (78 reputation)SSC Journeyman (78 reputation)SSC Journeyman (78 reputation)SSC Journeyman (78 reputation)

Group: General Forum Members
Points: 78 Visits: 134
Hello ! I understand that isolating services reduces the risk that one compromised service can be used to compromise others.
How about when you manage multiple sql servers? Is there a best practise, i.e. SQl server service accounts per service/per environment etc?

Thanks!
Paula
EricEyster
EricEyster
Right there with Babe
Right there with Babe (722 reputation)Right there with Babe (722 reputation)Right there with Babe (722 reputation)Right there with Babe (722 reputation)Right there with Babe (722 reputation)Right there with Babe (722 reputation)Right there with Babe (722 reputation)Right there with Babe (722 reputation)

Group: General Forum Members
Points: 722 Visits: 520
the prevailing wisdom is to use a separate service account for each server with the minimum permissions required to run the service.
sqlbuddy123
sqlbuddy123
SSCertifiable
SSCertifiable (5.9K reputation)SSCertifiable (5.9K reputation)SSCertifiable (5.9K reputation)SSCertifiable (5.9K reputation)SSCertifiable (5.9K reputation)SSCertifiable (5.9K reputation)SSCertifiable (5.9K reputation)SSCertifiable (5.9K reputation)

Group: General Forum Members
Points: 5916 Visits: 2243
paulaalkz 9229 (3/5/2014)
Hello ! I understand that isolating services reduces the risk that one compromised service can be used to compromise others.
How about when you manage multiple sql servers? Is there a best practise, i.e. SQl server service accounts per service/per environment etc?

Thanks!
Paula



There is always a trade-off. SQL server service accounts per environment is less secure but easy to manage. SQl server service accounts per service is more secure and managing is not that easy. Also depends on how big and complex the environment is. Obviously best practise, is SQL server service accounts per service.

--
SQLBuddy
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