The remote admin connections option controls whether a client application on a remote computer can use the Dedicated Administrator Connection (DAC).
The Dedicated Administrator Connection (DAC) lets an administrator access a running server to execute diagnostic functions or Transact-SQL statements, or to troubleshoot problems on the server, even when the server is locked or running in an abnormal state and not responding to a SQL Server Database Engine connection. In a cluster scenario, the administrator may not actually be logged on to the same node that is currently hosting the SQL Server instance and thus is considered “remote”. Therefore, this setting should usually be enabled (1) for SQL Server failover clusters; otherwise, it should be disabled (0) which is the default.
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 2.7
- Microsoft SQL Server Database 2016 CIS V1.3.0 - paragraph 2.7
- Microsoft SQL Server Database 2017 CIS V1.2.0 - paragraph 2.7
- Microsoft SQL Server Database 2019 CIS V1.2.0 - paragraph 2.7
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::remote_admin_connections_server_configuration_option_is_set_to_0: skip to your hiera data. This will skip this control for ALL databases.
mssql_secured::controls::remote_admin_connections_server_configuration_option_is_set_to_0::dbname: skip to your hiera data. This will skip this control for specified database only.
3) Add an entry with the content
remote_admin_connections_server_configuration_option_is_set_to_0 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.