public is a special fixed server role containing all logins. Unlike other fixed server roles, permissions can be changed for the public role. In keeping with the principle of least privileges, the public server role should not be used to grant permissions at the server scope as these would be inherited by all users.

Every SQL Server login belongs to the public role and cannot be removed from this role. Therefore, any permissions granted to this role will be available to all logins unless they have been explicitly denied to specific logins or user-defined server roles.

Excelent Compliance Solution.

Puppet is an excellent solution to ensure your databases are CIS or STIG compliant. Now you’re looking at information about only one compliance control, but managing total compliance isn’t hard either!

If you you like he prospect of easy way into continuous compliancy with minimal fuss and bother, we suggest taking a look at our solution as your go-to option. Plus, our team can help you get up and running so that you can focus on other areas of your business. What are you waiting for? Get started today!


This control is used in the following benchmarks:


To deliberately skip this control (e.g. meaning don’t use Puppet to enforce this setting), we provide you with three ways:

1) Add mssql_secured::controls::only_the_default_permissions_specified_by_microsoft_are_granted_to_the_public_server_role: skip to your hiera data. This will skip this control for ALL databases.
2) Add mssql_secured::controls::only_the_default_permissions_specified_by_microsoft_are_granted_to_the_public_server_role::dbname: skip to your hiera data. This will skip this control for specified database only.
3) Add an entry with the content only_the_default_permissions_specified_by_microsoft_are_granted_to_the_public_server_role to the array value mssql_secured::skip_list in your hiera data.


Attribute Name Short Description
title The database to apply the control to.


The database to apply the control to.

All controls need an database to apply the control to. Here is a simple example:

mssql_secured::controls::control_name {'MSSQLSERVER':}

In this example, the string DB is the database to apply the control to.

Back to overview of controls::only_the_default_permissions_specified_by_microsoft_are_granted_to_the_public_server_role