controls::sa login account has been renamed
Overview
The sa account is a widely known and often widely used SQL Server login with sysadmin privileges. The sa login is the original login created during installation and always has principal_id=1 and sid=0x01.
It is more difficult to launch password-guessing and brute-force attacks against the sa login if the name is not known.
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!
Benchmarks
This control is used in the following benchmarks:
- Microsoft SQL Server Database 2014 CIS V1.5.0 - paragraph 2.14
- Microsoft SQL Server Database 2016 CIS V1.3.0 - paragraph 2.14
- Microsoft SQL Server Database 2017 CIS V1.2.0 - paragraph 2.14
- Microsoft SQL Server Database 2019 CIS V1.2.0 - paragraph 2.14
Skipping
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::sa_login_account_has_been_renamed: skip
to your hiera data. This will skip this control for ALL databases.
2) Add mssql_secured::controls::sa_login_account_has_been_renamed::dbname: skip
to your hiera data. This will skip this control for specified database only.
3) Add an entry with the content sa_login_account_has_been_renamed
to the array value mssql_secured::skip_list
in your hiera data.
Attributes
Attribute Name | Short Description |
---|---|
preferred_value | The preferred value to use. |
title | The database to apply the control to. |
title
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::sa_login_account_has_been_renamed
preferred_value
The preferred value to use.
Some controls allow multiple values. The control implement a default value, but when you want an other value, you can use this parameter.
Type: Optional[String[1]]
Default:mssql_secured::lookup_setting('preferred_value', 'differt_sa')
Back to overview of controls::sa_login_account_has_been_renamed