http://www.sqlservercentral.com/blogs/basits-sql-server-tips/2013/04/24/the-public-role-a-potential-high-risk-security-concern-for-dbas/

Printed 2014/12/22 05:17AM

The Public Role – a potential high risk security concern for DBAs

By Basit Aalishan Masood-Al-Farooq, 2013/04/24

The public role is a special fixed-database role, which exists in every SQL Server database. The public role is different from all other database-level roles because in SQL Server, every database user is automatically assigned to the public database role, and you cannot remove public database role from SQL Server database. Although, permissions can be granted, revoked, and denied to the public role, however, granting or denying permissions to this role is not considered a best practice. This is because, when public role has permissions to do something, then every user in the database automatically gets this permission, which indeed is a high risk to database security. In addition this, when users have not been explicitly granted or denied permission on a securable object then users automatically inherits the permissions of public role. That is why, as per Microsoft Books Online and SQL Server Security best practice white paper, it is recommended to periodically review privileges granted to public role, and revoke any unnecessary privileges assigned to this role.

Checkout my article (The Public role – a potential high risk security concern for DBAs) on SSWUG.org, in which I discussed the security issues associated with the public database role, and how you can quickly find and remove privileges granted to the public database role in each database.



Copyright © 2002-2014 Simple Talk Publishing. All Rights Reserved. Privacy Policy. Terms of Use. Report Abuse.