What's the issue?
There are tempdb files on the C: drive, and there is more than 1 drive on the server.
Why is this a problem?
With one errant query, tempdb files can fill up and grow very quickly. If this file growth consume all available drive space on the C: drive, the operating system could freeze or crash.
What should you do about this?
If another drive is available, we highly recommend moving the tempdb files to another drive where the SQL Server service account has sufficient permissions. Because of the unpredictable usage and growth of tempdb files, we recommend isolating them to their own dedicated drive. Moving the files will require a restart of the SQL Server service.
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.