Title

Windows 2008 accounts must be configured to require passwords. (Cat I impact)

Discussion

The lack of password protection enables anyone to gain access to the information system, which opens a backdoor opportunity for intruders to compromise the system as well as other resources.

Check Content

Review the password required status for enabled user accounts. PowerShell must be installed on Windows 2008 to run the following. Open "Windows PowerShell" with elevated privileges (run as administrator). Domain Controllers: Enter 'Get-WMIObject -Class Win32_Useraccount -Filter "PasswordRequired=False" | FT Name, PasswordRequired, Disabled, Domain -AutoSize'. Exclude disabled accounts (e.g., Guest). Domain accounts requiring smart card (CAC/PIV) may also be excluded. If any enabled user accounts are returned with a "PasswordRequired" status of "False", this is a finding. Member servers and standalone systems: Enter 'Get-WMIObject -Class Win32_Useraccount -Filter "PasswordRequired=False and LocalAccount=True" | FT Name, PasswordRequired, Disabled, LocalAccount'. Exclude disabled accounts (e.g., Guest). If any enabled user accounts are returned with a "PasswordRequired" status of "False", this is a finding. Note: Other queries or tools may be used. The organization must be able to demonstrate the results are valid and meet the intent of the requirement.

Fix Text

Configure all enabled accounts to require passwords. The password required flag can be set by entering the following on a command line: "Net user [username] /passwordreq:yes", substituting [username] with the name of the user account.

Additional Identifiers

Rule ID: SV-29549r2_rule

Vulnerability ID: V-7002

Group Title: Password Requirement

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.