Multiple choice technology security

During testing you observed that after few minutes of initiating the scan appscan locks itself out of the application. How will you resolve the problem?

  1. Configure appscan not to test login/logout pages

  2. Increase the thread count

  3. Decrease the timeout

  4. Increase the timeout
Reveal answer Fill a bubble to check yourself
A Correct answer
Explanation

AppScan lockout occurs when automated testing triggers account lockout mechanisms. Repeatedly testing login/logout pages causes multiple failed login attempts. Excluding these pages (A) prevents AppScan from triggering the lockout while still scanning other functionality. Thread count (B) and timeout settings (C, D) don't address account lockout logic.

AI explanation

If a scan trips account lockout policies within minutes, it's almost always because AppScan is repeatedly hitting login/logout functionality with test payloads, exhausting the allowed failed-attempt count. The fix is to explicitly exclude the login/logout pages from testing so the scanner doesn't keep triggering the app's own lockout defenses; adjusting thread count or timeout settings doesn't address the root cause.

Keep practicing — related questions