What's the issue?
C2 audit mode in SQL Server is a legacy security feature that enables auditing of system-level activities in compliance with the U.S. Department of Defense "C2" security standard.
Why is this a problem?
C2 audit mode is deprecated, and is no longer considered a best practice for auditing activity. Not only can it negatively impact performance, but also it can result in the SQL Server instance shutting down automatically if the audit files run out of storage space.
What should you do about this?
Unless you are required to use C2 audit mode for very old and unsupported versions of SQL Server, we recommend auditing activity using SQL Audit feature that was introduced with SQL Server 2008.
Read more...
Vulnerability
Category
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.