controls::windows builtin groups are not sql logins
Prior to SQL Server 2008, the BUILTIN\Administrators group was added as a SQL Server login with sysadmin privileges during installation by default. Best practices promote creating an Active Directory level group containing approved DBA staff accounts and using this controlled AD group as the login with sysadmin privileges. The AD group should be specified during SQL Server installation and the BUILTIN\Administrators group would therefore have no need to be a login.
The BUILTIN groups (Administrators, Everyone, Authenticated Users, Guests, etc.) generally contain very broad memberships which would not meet the best practice of ensuring only the necessary users have been granted access to a SQL Server instance. These groups should not be used for any level of access into a SQL Server Database Engine instance.
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:
- Microsoft SQL Server Database 2014 CIS V1.5.0 - paragraph 3.9
- Microsoft SQL Server Database 2016 CIS V1.3.0 - paragraph 3.9
- Microsoft SQL Server Database 2017 CIS V1.2.0 - paragraph 3.9
- Microsoft SQL Server Database 2019 CIS V1.2.0 - paragraph 3.9
To deliberately skip this control (e.g. meaning don’t use Puppet to enforce this setting), we provide you with three ways:
mssql_secured::controls::windows_builtin_groups_are_not_sql_logins: skip to your hiera data. This will skip this control for ALL databases.
mssql_secured::controls::windows_builtin_groups_are_not_sql_logins::dbname: skip to your hiera data. This will skip this control for specified database only.
3) Add an entry with the content
windows_builtin_groups_are_not_sql_logins 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:
In this example, the string DB is the database to apply the control to.
Back to overview of controls::windows_builtin_groups_are_not_sql_logins