You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The "Weak Password" check doesn't check only for weak passwords against a list of less known weak passwords but it will also be flagged if the Enforce password policy or Enforce password expiration isn't checked (for enabled accounts).
I can have a login with a good password (length and complexity) but still, the message will be "Some SQL logins have weak passwords.". This brings confusion.
In this case, the reason can be one of the unchecked boxes.
Suggestion
Current:
"displayName": "SQL logins have weak passwords",
"description": "Some SQL logins have weak passwords. Make sure that you use a strong password for each of your SQL logins to decrease vulnerabilities.",
An idea:
"displayName": "SQL logins have weak passwords or missing policy/expiration",
"description": "Some SQL logins have weak passwords or don't have the policy/expiration check on. Make sure that you use a strong password for each of your SQL logins and change your passwords often to decrease vulnerabilities.",
The text was updated successfully, but these errors were encountered:
The "Weak Password" check doesn't check only for weak passwords against a list of less known weak passwords but it will also be flagged if the
Enforce password policy
orEnforce password expiration
isn't checked (for enabled accounts).That said, the description of this check (and the title too) should be refined to a more complete message.
https://github.com/microsoft/sql-server-samples/blob/master/samples/manage/sql-assessment-api/ruleset.json#L3501
I can have a login with a good password (length and complexity) but still, the message will be "Some SQL logins have weak passwords.". This brings confusion.
In this case, the reason can be one of the unchecked boxes.
Suggestion
Current:
An idea:
The text was updated successfully, but these errors were encountered: