sp_check: SQL Server Database Checks

Invalid Windows login

What's the issue?

One or more logins have been verified as invalid Windows accounts.

Why is this a problem?

Having random permissions for invalid accounts makes for messy permissions. Clean up the mess.

What should you do about this?

Find and remove any permissions for the login. These can be inside a database, in a instance level role, or even ownership of databases or jobs. Only delete the login after removing all permissions, as simply deleting the login may result in lingering orphaned permissions and may cause issues with anything owned by the login.

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.