controls::clr assembly permission set is set to safe access for all clr assemblies

Overview

Setting CLR Assembly Permission Sets to SAFE_ACCESS will prevent assemblies from accessing external system resources such as files, the network, environment variables, or the registry.

Assemblies with EXTERNAL_ACCESS or UNSAFE permission sets can be used to access sensitive areas of the operating system, steal and/or transmit data and alter the state and other protection measures of the underlying Windows Operating System.

Assemblies which are Microsoft-created (is_user_defined = 0) are excluded from this check as they are required for overall system functionality.

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

Attributes

Attribute Name Short Description
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::clr_assembly_permission_set_is_set_to_safe_access_for_all_clr_assemblies