controls::unnecessary sql server protocols are set to disabled

Overview

SQL Server supports Shared Memory, Named Pipes, and TCP/IP protocols. However, SQL Server should be configured to use the bare minimum required based on the organization’s needs.

Using fewer protocols minimizes the attack surface of SQL Server and, in some cases, can protect it from remote attacks.

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:

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

Attributes

Attribute Name Short Description
np_enabled  
sm_enabled  
tcp_enabled  
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::unnecessary_sql_server_protocols_are_set_to_disabled

tcp_enabled

This is the Booleand value containing information if Tcp protocol is enabled in the SQL Server instance. Type: Optional[Boolean]

Default:mssql_secured::lookup_setting('tcp_enabled', undef)

Back to overview of controls::unnecessary_sql_server_protocols_are_set_to_disabled

np_enabled

This is the Booleand value containing information if Np protocol is enabled in the SQL Server instance. Type: Optional[Boolean]

Default:mssql_secured::lookup_setting('np_enabled', undef)

Back to overview of controls::unnecessary_sql_server_protocols_are_set_to_disabled

sm_enabled

This is the Booleand value containing information if SM protocol is enabled in the SQL Server instance. Type: Optional[Boolean]

Default:mssql_secured::lookup_setting('sm_enabled', undef)

Back to overview of controls::unnecessary_sql_server_protocols_are_set_to_disabled