What's the issue?
One or more logins or groups has been included in the db_accessadmin, db_securityadmin, or db_ddladmin database roles in a user database.
Why is this a problem?
These roles noted have very specific purposes, but we have found that often users have been assigned to these roles while also being assigned to the db_owner role. Since the db_owner role includes all permissions from the db_accessadmin, db_securityadmin, and db_ddladmin roles, these permissions can be redundant.
What should you do about this?
Routinely review the members of the db_accessadmin, db_securityadmin, and db_ddladmin roles of user databases to ensure that membership in these roles is assigned correctly and not to members of the db_owner role.
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.