TMA-MSSQL-2.17
Ensure 'clr strict security' Server Configuration Option is set to '1'
HighLevel 1Automatedmssql
Description
The clr strict security option specifies whether the engine applies the PERMISSION_SET on the assemblies. Both value and value_in_use must equal 1. Default: By default, this option is Enabled (1). Runs one sqlcmd query with its defaults (Windows authentication to the local default instance); set SQLCMDSERVER, SQLCMDUSER and SQLCMDPASSWORD for another instance or SQL authentication. Needs VIEW SERVER STATE / sysadmin-level read access.
How it is checked
Audit method: SQL query
sql_query
sqlcmd -b -h -1 -W -Q "SET NOCOUNT ON; SELECT CASE WHEN CAST(value AS int) = 1 AND CAST(value_in_use AS int) = 1 THEN 'compliant' ELSE 'noncompliant' END FROM sys.configurations WHERE name = 'clr strict security';"- Expected output
compliant
How it is fixed
Fix method: SQL statement
shell
sqlcmd -b -h -1 -W -Q "SET NOCOUNT ON; EXEC sp_configure 'show advanced options', 1; RECONFIGURE; EXEC sp_configure 'clr strict security', 1; RECONFIGURE; EXEC sp_configure 'show advanced options', 0; RECONFIGURE;"Properties
- Operating systems
- Any
- Tags
- mssqldatabasesurface-area
- Reference
- CIS Microsoft SQL Server 2025 Benchmark v1.0.0 - 2.17 Ensure 'clr strict security' Server Configuration Option is set to '1'
Check this host
Run this on a machine you are allowed to audit. The scan is read-only.
shell
tmaegis scan --target mssql