Objective 2.04 Refine Policy Structure for Policy Elements (e.g., URLs, Parameters, Files Types, Headers, Sessions and Logins, Content Profiles, CSRF Protection, Anomaly Protection) 303 Practice Questions (Page 5)

Questions 21–24

1. 21foundation · easy

   In ASM, what is the purpose of configuring login protection for a session?

   • ATo encrypt session cookies
   • BTo provide single sign-on functionality
   • CTo manage user roles and permissions
   • DTo detect and prevent brute-force attacks on login pages
   Reveal Solution Discussion Select an answer first
2. 22expert · hard

   A web application has a URL /api/v1/users that accepts a JSON payload with a 'role' parameter. The application supports roles 'admin', 'user', and 'guest'. The ASM policy is in blocking mode and is blocking legitimate requests that include a 'role' value with a leading or trailing space (e.g., ' admin'). You need to allow these requests while still enforcing the allowed roles. What should you configure?

   • ASet the parameter 'role' to allow all values.
   • BIncrease the maximum length of the parameter.
   • CDisable the parameter policy for 'role'.
   • DCreate a parameter policy for 'role' that allows a regular expression that matches the allowed roles with optional leading/trailing spaces.
   Reveal Solution Discussion Select an answer first
4. 23application · medium

   A web application has a login page that uses a CAPTCHA to prevent automated attacks. The ASM policy is in blocking mode and is blocking legitimate users who complete the CAPTCHA correctly. You need to allow these users while still protecting against brute force attacks. What should you configure?

   • ADisable login protection for the login page.
   • BIncrease the failed login attempt threshold.
   • CUse the anomaly detection to block only suspicious IPs.
   • DConfigure the login protection to ignore requests that include a valid CAPTCHA.
   Reveal Solution Discussion Select an answer first
5. 24application · medium

   A company's web application has a login page that is being targeted by credential stuffing attacks. The security team wants to block repeated failed login attempts from the same IP address. The ASM policy is in blocking mode. What should you configure?

   • AUse the anomaly detection to block the IP after a high number of requests.
   • BDisable the login page to prevent attacks.
   • CCreate a URL policy that blocks the login page after a certain number of requests.
   • DEnable the login protection feature and set a threshold for failed login attempts.
   Reveal Solution Discussion Select an answer first