sp_check: SQL Server Database Checks

CLR enabled

What's the issue?

You have the instance configuration 'clr enabled' set to enabled.

Why is this a problem?

It is possible to do things in an assembly with a PERMISSION_SET value of UNSAFE that cannot be done in regular T-SQL, similarly to extended stored procedures, xp_cmdshell, and the OLE Automatic procedures.

What should you do about this?

Review with your team to see if you need CLR enabled in your SQL Server instance. If you do and your SQL Server instance version SQL Server 2017 or later, we recommend you disabling 'clr enabled' and enabling 'clr strict security' instead.

You can disable 'clr enabled' with the following T-SQL.

EXEC sp_configure 'clr enabled', 0;

What do the Vulnerability Levels mean?

0 - Information only. This is stuff you should know about your instances like version and service account used, but if you don't know it…well, now you do.

1 - High vulnerability requiring action. These are the issues that could most likely lead to your company being front page news for all the wrong reasons. If your instances have any results at this level then we recommend cancelling that 3-martini lunch and instead huddling with your team to figure out when to address these issues.

2 - High vulnerability to review. These include settings and assigned permissions you should review soon, if not immediately. These findings may not necessarily indicate a clear vulnerability, but we've found unexpected vulnerabilities in these categories at many, many clients.

3 - Potential vulnerability to review. These are configurations or assigned permissions you may be using that could lead to problems for users. Or maybe they're just required for your applications. Either way, we recommend reviewing these to make sure these are correct.

4 – Low vulnerability with recommended action. These are typically security inconsistencies that should be addressed. They aren't likely to cause problems, but you should clean up the mess.