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