WTM must be configured to store passwords using an approved salted key derivation function, preferably using a keyed hash for password-based authentication.

Passwords must be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised.

Network devices must enforce cryptographic representations of passwords when storing passwords in databases, configuration files, and log files. Passwords must be protected at all times; using a strong one-way hashing encryption algorithm with a salt is the standard method for providing a means to validate a password without having to store the actual password.

Performance and time required to access are factors that must be considered, and the one way hash is the most feasible means of securing the password and providing an acceptable measure of password security. If passwords are stored in clear text, they can be plainly read and easily compromised.

In many instances, verifying the user knows a password is performed using a password verifier. In its simplest form, a password verifier is a computational function that is capable of creating a hash of a password and determining if the value provided by the user matches the stored hash.

1. Log in to the WTM Web UI. 2. Navigate to Admin >> User Management >> Login Control. 3. Verify "Login Control" is enabled and "GUI Idle Timeout" is set to at least 300 seconds. 4. Log in to the SSH CLI. 5. Enter "configure terminal". 6. Enter "show running-config | include session".

If "session idle-timeout" is absent or does not say at least 300 for both the CLI and GUI, this is a finding.

1. Log in to the WTM Web UI. 2. Navigate to Admin >> User Management >> Login Control. 3. Click "Enable". 4. Set the "GUI Idle Timeout" to "300 seconds". 5. Click "Commit". 6. Log in to the SSH CLI. 7. Enter "configure terminal". 8. Enter "session idle-timeout 300". 9. Enter "Commit" and then press "Enter".