Security infrastructure plan

From: Chris Beardsley (clb39@nospam-cornell.edu)
Date: 05/09/02 

From: "Chris Beardsley" <clb39@nospam-cornell.edu>
Date: Thu, 9 May 2002 13:08:39 -0400

The DB's on our local test Server currently has everyone in the public role.
The public role has access to everything. This occurs to me to be a wide
open security schema (or does not exist, whichever your preference).

I was planning on making some more tiered access groups, then restricting
public to select only. The results would look something like this:

Full - all rights to select, insert, update, delete, and DRI - System table
access
Change - Rights to select, insert, update, and delete Denied DRI and system
table access
Public - Rights to select Denied Insert, Update, Delete and DRI and system
table access
Purgatory - Denied access to everything and system table access

What am I missing with this user formula? What could I potentially break on
the server (not App) if I implement this?

Responses directly to this, or additional security information would be
greatly appreciated.

Chris

Relevant Pages

  • SQL 6.5 - Rights - Not Working Correctly
    ... someone granted the SQL PUBLIC role with ... matter what specific rights you granted via user-defined ... The PUBLIC role has SELECT, INSERT, UPDATE & DELETE ... >rights issue with for certain SQL users that are a member ...
    (microsoft.public.sqlserver.security)
  • Re: Removing Permissions from the public role
    ... did you think about putting those 8 tables in a different schema, and then just granting rights to that schema, revoking the rights for that group from public. ... that user and ran some grant scripts to allow them to select from the 8 ... I see that there is a public role ... the public security role is still allowing the new login access to all ...
    (microsoft.public.sqlserver.setup)
  • Re: Problem with role permissions
    ... " We are trying to set the premissions for the role. ... created and the public role. ... I would run profiler to capture this. ... This posting is provided AS IS with no warranties, and confers no rights. ...
    (microsoft.public.sqlserver.security)
  • Re: DTS permissions to create
    ... The way I'd do it is remove (revoke and not deny) the exec ... rights from the public role and then create your own role with exec rights ...
    (microsoft.public.sqlserver.server)