GPEN · Question #364
John works as a professional Ethical Hacker. He has been assigned a project to test the security server. Now, he suggests some countermeasures to avoid such brute force attacks on the We- aresecure se
The correct answer is A. The site should use CAPTCHA after a specific number of failed login attempts. B. The site should restrict the number of login attempts to only three times.. Effective brute force countermeasures directly limit or block repeated automated login attempts using CAPTCHA and account lockout policies.
Question
John works as a professional Ethical Hacker. He has been assigned a project to test the security server. Now, he suggests some countermeasures to avoid such brute force attacks on the We- aresecure server. Which of the following are countermeasures against a brute force attack? Each correct answer represents a complete solution. Choose all that apply.
Options
- AThe site should use CAPTCHA after a specific number of failed login attempts.
- BThe site should restrict the number of login attempts to only three times.
- CThe site should force its users to change their passwords from time to time.
- DThe site should increase the encryption key length of the password.
How the community answered
(21 responses)- A76% (16)
- C10% (2)
- D14% (3)
Why each option
Effective brute force countermeasures directly limit or block repeated automated login attempts using CAPTCHA and account lockout policies.
CAPTCHA challenges distinguish human users from automated scripts by requiring a cognitive task that bots cannot reliably solve. Presenting CAPTCHA after a threshold of failed attempts effectively neutralizes brute force and credential-stuffing tools that rely on high-speed automated submission.
Restricting login attempts to three directly defeats brute force attacks by triggering a lockout or enforced delay after the threshold is exceeded. This makes exhaustive trial-and-error attacks impractical because attackers cannot cycle through large password sets against a specific account.
Periodic password changes reduce the window of exposure for a compromised credential but do not prevent or interrupt an active brute force attack against the current password.
Increasing the encryption key length strengthens cryptographic protection of stored or transmitted data but has no effect on an attacker submitting login guesses through a web form.
Concept tested: Brute force attack prevention - lockout and CAPTCHA controls
Source: https://owasp.org/www-community/attacks/Brute_force_attack
Topics
Community Discussion
No community discussion yet for this question.