Authentication mode in SQL Server

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2008 » SQL Server 2008 - General » Authentication mode in SQL Server

14 posts, Page 2 of 2

««1 2

Authentication mode in SQL Server

Rate Topic

Display Mode

Topic Options

Author

Message

Jack Corbett

Posted Wednesday, January 11, 2012 10:27 AM

SSChampion

Group: General Forum Members
Last Login: Friday, May 17, 2013 12:22 PM
Points: 10,571, Visits: 11,871

Dev (1/11/2012)

If somebody can login to Application Server & read configuration files, he can delete website as well (worst scenario).

SQL Server Logins are manageable for Web Applications. Few logins (Logical Grouping based on roles) can manage overall database operation for the Web Users. I don’t find it logical to create 1000 Users / Logins in database until I have explicit Audit Requirements to track each user’s activity.

Sure, the problem is bigger if they can get to the config files, but why have the DB Exposed at all?

You don't have to create a login for every user to use Windows Authentication if you use the first option I mention. It is still basically using an application login, it is just using an AD account for the app pool instead of SQL Authentication.

You can also use AD groups to limit the # of logins you create. Then login is managed through AD groups and, if you are using least privileges, that works fine.

Jack Corbett

Applications Developer

Don't let the good be the enemy of the best. -- Paul Fleming

Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
How to Post Performance Problems
Crosstabs and Pivots or How to turn rows into columns Part 1
Crosstabs and Pivots or How to turn rows into columns Part 2

Post #1234180

Steve Jones - SSC Editor

Posted Wednesday, January 11, 2012 10:28 AM

SSC-Dedicated

Group: Administrators
Last Login: Today @ 3:30 PM
Points: 31,436, Visits: 13,751

Dev (1/11/2012)

If somebody can login to Application Server & read configuration files, he can delete website as well (worst scenario).

I wouldn't count out some SQL Injection or XSS style attack here. Config files may or may not be more secure than the services configurations, but admins can't get the password from the services items. The password isn't exposed. They could read it, and give a password to someone else when it's it a config file.

Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help

Post #1234181

Dev

Posted Wednesday, January 11, 2012 10:43 AM

SSCrazy

Group: General Forum Members
Last Login: Wednesday, May 15, 2013 2:05 PM
Points: 2,013, Visits: 1,566

If you are an Everything DBA (Hybrid DBA) then AD management falls in your bucket. I believe AD Management is out-of-scope to DBA roles (in general). However it’s a nice option & I am not denying it.

~Dev~

Post #1234197

Dev

Posted Wednesday, January 11, 2012 10:50 AM

SSCrazy

Group: General Forum Members
Last Login: Wednesday, May 15, 2013 2:05 PM
Points: 2,013, Visits: 1,566

Also, Security Measures are based on trust model. If we can’t rely on Administrators (which we shouldn’t) of your application / database then we can’t rely on anyone.

I am aware of incidences where Admin were guilty for security breaches. But should we distrust all?

I remember a recent post in SSC where OP asked to encrypt the data from DBAs for HR modules. Funny though, it’s a valid requirement.

~Dev~

Post #1234205

« Prev Topic | Next Topic »

14 posts, Page 2 of 2

««1 2

Permissions