Which TWO techniques are highly effective at mitigating the risk of Pass-the-Hash (PtH) attacks in a Windows environment?
Trap 1: Increasing password rotation frequency to every 24 hours
While frequent password rotation is a good practice for preventing long-term credential reuse, it does not prevent a Pass-the-Hash attack. An attacker only needs the current NTLM hash of a valid user to authenticate successfully; the age of the password is irrelevant to the success of the attack.
Trap 2: Enabling cleartext password logging in Group Policy
Enabling cleartext password logging is a dangerous security configuration that would significantly increase the risk to an organization. This would store sensitive credentials in logs, making it trivial for an attacker to obtain cleartext passwords, which is the exact opposite of a secure defensive posture.
Trap 3: Requiring 32-character passwords for all users
Increasing password length does nothing to prevent Pass-the-Hash. Since PtH bypasses the need for the original password, the length or complexity of the user's password does not impede the attacker. The hash remains the target, and the hash remains valid regardless of the password's original length.
- A
Disabling NTLM authentication in favor of Kerberos
Kerberos is significantly more secure than NTLM because it utilizes ticket-based authentication. Unlike NTLM, which can be easily replayed without knowing the password, Kerberos tickets have expiration times and require interaction with the Key Distribution Center, effectively neutralizing the core mechanism that makes Pass-the-Hash attacks possible.
- B
Increasing password rotation frequency to every 24 hours
Why it fails: While frequent password rotation is a good practice for preventing long-term credential reuse, it does not prevent a Pass-the-Hash attack. An attacker only needs the current NTLM hash of a valid user to authenticate successfully; the age of the password is irrelevant to the success of the attack.
- C
Implementing Restricted Admin mode for Remote Desktop
Restricted Admin mode for RDP ensures that credentials are not sent to the remote machine during an RDP session. By preventing the caching of user credentials in the remote system's memory, this feature effectively stops attackers from dumping those hashes from the remote host after a successful RDP login.
- D
Enabling cleartext password logging in Group Policy
Why it fails: Enabling cleartext password logging is a dangerous security configuration that would significantly increase the risk to an organization. This would store sensitive credentials in logs, making it trivial for an attacker to obtain cleartext passwords, which is the exact opposite of a secure defensive posture.
- E
Requiring 32-character passwords for all users
Why it fails: Increasing password length does nothing to prevent Pass-the-Hash. Since PtH bypasses the need for the original password, the length or complexity of the user's password does not impede the attacker. The hash remains the target, and the hash remains valid regardless of the password's original length.