controls::ole automation procedures server configuration option is set to 0
Overview
The Ole Automation Procedures option controls whether OLE Automation objects can be instantiated within Transact-SQL batches. These are extended stored procedures that allow SQL Server users to execute functions external to SQL Server.
Enabling this option will increase the attack surface of SQL Server and allow users to execute functions in the security context of SQL Server.
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:
- Microsoft SQL Server Database 2014 CIS V1.5.0 - paragraph 2.5
- Microsoft SQL Server Database 2016 CIS V1.3.0 - paragraph 2.5
- Microsoft SQL Server Database 2017 CIS V1.2.0 - paragraph 2.5
- Microsoft SQL Server Database 2019 CIS V1.2.0 - paragraph 2.5
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::ole_automation_procedures_server_configuration_option_is_set_to_0: skip
to your hiera data. This will skip this control for ALL databases.
2) Add mssql_secured::controls::ole_automation_procedures_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 ole_automation_procedures_server_configuration_option_is_set_to_0
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::ole_automation_procedures_server_configuration_option_is_set_to_0