Non-clustered SQL Server instances within production environments should be designated as hidden to prevent advertisement by the SQL Server Browser service.

Designating production SQL Server instances as hidden leads to a more secure installation because they cannot be enumerated. However, clustered instances may break if this option is selected.

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::hide_instance_option_is_set_to_yes_for_production_sql_server_instances: skip to your hiera data. This will skip this control for ALL databases.
2) Add mssql_secured::controls::hide_instance_option_is_set_to_yes_for_production_sql_server_instances::dbname: skip to your hiera data. This will skip this control for specified database only.
3) Add an entry with the content hide_instance_option_is_set_to_yes_for_production_sql_server_instances 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::hide_instance_option_is_set_to_yes_for_production_sql_server_instances