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


Managing security and Certificates


Managing security and Certificates

Author
Message
Dean Jones-454305
Dean Jones-454305
Old Hand
Old Hand (378 reputation)Old Hand (378 reputation)Old Hand (378 reputation)Old Hand (378 reputation)Old Hand (378 reputation)Old Hand (378 reputation)Old Hand (378 reputation)Old Hand (378 reputation)

Group: General Forum Members
Points: 378 Visits: 1130
Hi All

I have heard about the various enhancements to security configuration in SQL 2005, I was wondering how other people manage SQL logins in your respective environment, how would you manage users, I assume we all script this, what if a user needs access to update a table, would you simply open your script and change this to reflect the new change ?

Also, I have heard about certificates and was wondering how these are used and in what circumstances would you use certificates ?

I have a situation where an application needs SQL access to a database, this involves giving developers the application login and also the password as well, I was wondering whether are any alternatives to taking this approach ?

Also, how can I further lock SQL down to make sure that its only that application which can use that login, in effect stopping other people from using the login meant for the application.
Jonathan Kehayias
Jonathan Kehayias
SSCrazy
SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)

Group: General Forum Members
Points: 2962 Visits: 1807
Dean Jones (5/12/2009)

I have a situation where an application needs SQL access to a database, this involves giving developers the application login and also the password as well, I was wondering whether are any alternatives to taking this approach ?

Also, how can I further lock SQL down to make sure that its only that application which can use that login, in effect stopping other people from using the login meant for the application.


I manage this by having different passwords in Production and Development for the application logins. Developers can develop using their own logins to the SQL Server for the most part. When it comes to testing, the app login is generally good to use so that the permissions are correctly scripted when migrating to production.

If you want to block a login from accessing SQL Server except from a specific application name, you can look at the following blog post I made last year:

http://sqlblog.com/blogs/jonathan_kehayias/archive/2008/06/18/securing-production-servers-from-developers-with-ssms-and-application-usernames-passwords.aspx

Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs
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