Detections
Analytics

1.1.1.1.3.5 Set 'Password must meet complexity requirements' to 'Enabled'

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

This policy setting checks all new passwords to ensure that they meet basic requirements for strong passwords. When this policy is enabled, passwords must meet the following minimum requirements: #x2022; Not contain the user's account name or parts of the user's full name that exceed two consecutive characters #x2022; Be at least six characters in length #x2022; Contain characters from three of the following four categories: #x2022; English uppercase characters (A through Z) #x2022; English lowercase characters (a through z) #x2022; Base 10 digits (0 through 9) #x2022; Non-alphabetic characters (for example, !, $, #, %) #x2022; A catch-all category of any Unicode character that does not fall under the previous four categories. This fifth category can be regionally specific. Each additional character in a password increases its complexity exponentially. For instance, a seven-character, all lower-case alphabetic password would have 267 (approximately 8 x 109 or 8 billion) possible combinations. At 1,000,000 attempts per second (a capability of many password-cracking utilities), it would only take 133 minutes to crack. A seven-character alphabetic password with case sensitivity has 527 combinations. A seven-character case-sensitive alphanumeric password without punctuation has 627 combinations. An eight-character password has 268 (or 2 x 1011) possible combinations. Although this might seem to be a large number, at 1,000,000 attempts per second it would take only 59 hours to try all possible passwords. Remember, these times will significantly increase for passwords that use ALT characters and other special keyboard characters such as '!' or '@'. Proper use of the password settings can help make it difficult to mount a brute force attack. Passwords that contain only alphanumeric characters are extremely easy to discover with several publicly available tools.

Solution

Navigate to the Group Policy UI path expressed in the Audit procedure and set Password must meet complexity requirements as recommended.

Impact- If the default password complexity configuration is retained, additional help desk calls for locked-out accounts could occur because users might not be accustomed to passwords that contain non-alphabetic characters. However, all users should be able to comply with the complexity requirement with minimal difficulty. If your organization has more stringent security requirements, you can create a custom version of the Passfilt.dll file that allows the use of arbitrarily complex password strength rules. For example, a custom password filter might require the use of non-upper row characters. (Upper row characters are those that require you to hold down the SHIFT key and press any of the digits between 1 and 0.) A custom password filter might also perform a dictionary check to verify that the proposed password does not contain common dictionary words or fragments. Also, the use of ALT key character combinations can greatly enhance the complexity of a password. However, such stringent password requirements can result in unhappy users and an extremely busy help desk. Alternatively, your organization could consider a requirement for all administrator passwords to use ALT characters in the 0128#x00E2;#x20AC;#x201C;0159 range. (ALT characters outside of this range can represent standard alphanumeric characters that would not add additional complexity to the password.)

See Also

https://workbench.cisecurity.org/files/42

Item Details

Category: IDENTIFICATION AND AUTHENTICATION

References: 800-53|IA-5(1), CCE|CCE-3442-1

Plugin: Windows

Control ID: dcb4cb9af28b09938db93a4e8e1495210b5d10d83f357d8945645a284d7f6d9b