Microsoft Best Practices recommend to use at least a 2048-bit encryption algorithm for asymmetric keys.

The RSA_2048 encryption algorithm for asymmetric keys in SQL Server is the highest bit-level provided and therefore the most secure available choice (other choices are RSA_512 and RSA_1024).

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