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


SQL Server security Standard


SQL Server security Standard

Author
Message
lianv 90648
lianv 90648
SSC Rookie
SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)

Group: General Forum Members
Points: 30 Visits: 121
Good Day ,
we are in the process of implementing a new security policy where we plant to grant execute permissions to all the stored procedures to public in the user database and limit the access to the tables to designated roles. Will that be an acceptable security standard ? Or should we rather stick to the traditional standard whereby we grant execute permissions to the designated roles ?
Evil Kraig F
Evil Kraig F
SSC-Insane
SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)

Group: General Forum Members
Points: 21159 Visits: 7660
lianv 90648 (1/18/2011)
Good Day ,
we are in the process of implementing a new security policy where we plant to grant execute permissions to all the stored procedures to public in the user database and limit the access to the tables to designated roles. Will that be an acceptable security standard ? Or should we rather stick to the traditional standard whereby we grant execute permissions to the designated roles ?


It is not best practice, but I know of a number of businesses that allow this for ease of use. You will want to make sure any databases that store incredibly damaging data though (client credit card numbers, for example) do NOT use this practice.

This usually is done when a select few, if more than one, IIS SQL login actually access any specific server. If the Login is broken, and that's your most likely point of hack/security failure, then public or private won't matter much. If each application is specific to its login, and you run multiple applications off a single server, then you won't want to pursue the 'easy' method, and do it right, just as a CYA.


- Craig Farrell

Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

For better assistance in answering your questions | Forum Netiquette
For index/tuning help, follow these directions. |Tally Tables

Twitter: @AnyWayDBA
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