Local Windows groups should not be used as logins for SQL Server instances.
Allowing local Windows groups as SQL Logins provides a loophole whereby anyone with OS level administrator rights (and no SQL Server rights) could add users to the local Windows groups and thereby give themselves or others access to the SQL Server 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 2016 CIS V1.3.0 - paragraph 3.10
- Microsoft SQL Server Database 2017 CIS V1.2.0 - paragraph 3.10
- Microsoft SQL Server Database 2019 CIS V1.2.0 - paragraph 3.10
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_local_groups_are_not_sql_logins: skip to your hiera data. This will skip this control for ALL databases.
mssql_secured::controls::windows_local_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_local_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.