Free NSE5_FWB_AD-8.0 Exam Braindumps
Fortinet NSE 5 - FortiWeb 8.0 Administrator Questions 11–15 (page: 4)

Updated On: 22-Aug-2026

You have configured parameter validation, file security, and machine learning (ML) anomaly detection for a web form, but some server-side request forgery tests are still succeeding. You need to advise the team on what to prioritize next to improve SSRF protection without compromising other parts of the application.
Which recommendation would best strengthen FortiWeb's ability to block remaining SSRF attempts?

  1. Disable ML anomaly detection and rely solely on parameter inspection.
  2. Apply HTTPS inspection at the transport layer, which FortiWeb does not use to block SSRF.
  3. Offload all server-side request forgery (SSRF) protection to FortiGate and remove FortiWeb from the API
    flow.
  4. Review and refine input validation logic, as SSRF may be exploiting backend behavior or bypassing weak filters.

Answer(s): D

Explanation:

SSRF often succeeds when application input is passed to back-end services that make outbound requests. Refining input validation logic helps FortiWeb better detect and block unsafe URLs, internal addresses, metadata endpoints, redirects, or encoded payloads while preserving the existing protections for the rest of the application.



While reviewing FortiWeb logs, you notice a suspicious login request that failed authentication. You suspect it may be part of an injection attack targeting the login form.
Which input pattern is an example of a typical SQL injection attempt that could bypass authentication checks?

  1. <script>document.location='/steal?cookie='+document.cookie</script>
  2. SELECT username FROM accounts WHERE username='admin';-- ' AND
    password='password';
  3. '||(SELECT password FROM users WHERE role='admin')||'
  4. <sql>select(ALL USERS);</sql>

Answer(s): B

Explanation:

This pattern uses SQL syntax and a comment sequence to alter the intended login query logic. The comment marker can cause the remaining password condition to be ignored, which is a common SQL injection technique used to bypass authentication checks.



Refer to the exhibit.

You have deployed FortiWeb behind a FortiGate that is configured as a reverse proxy and inserts the X-Forwarded-For HTTP header when forwarding HTTP and HTTPS traffic.
FortiWeb is using a custom inline protection profile, and logging is enabled, as shown in the exhibit.
You notice that FortiWeb is blocking legitimate users, and all requests in the attack logs appear to come from the FortiGate IP address, not the original client IP addresses.
Which action should you take to fix this issue?

  1. Modify the protection profile to use the X-Forwarded-For header for client IP address detection.
  2. Replace the current deployment mode with a one-arm proxy to expose source IP addresses.
  3. Recreate the server policy using the predefined profile instead of a custom one.
  4. Disable IP-based detection features on FortiWeb to avoid IP-related blocking.

Answer(s): A

Explanation:

FortiGate is acting as the upstream proxy, so FortiWeb sees the FortiGate address as the source unless it is configured to trust and read the X-Forwarded-For header. Using that header for client IP detection allows FortiWeb to apply logging, rate-based controls, and IP-based protections to the real client addresses instead of incorrectly treating all traffic as coming from FortiGate.



Refer to the exhibit.

There is only one administrator account configured on FortiWeb and IPv6 is not configured on any interface.
Which action should an administrator take to restrict any brute force attacks that attempt to gain access to the FortiWeb management GUI?

  1. Replace 0.0.0.0/0 with a specific IP address.
  2. Make configuration changes on the upstream device.
  3. Change the setting in the Access Profile field to Read_Only.
  4. Delete the built-in administrator user and create a new one.

Answer(s): A

Explanation:

The trusted hosts setting should allow management access only from a specific trusted administrator IP address or subnet. Leaving 0.0.0.0/0 permits access attempts from any IPv4 source, increasing exposure to brute force attacks against the FortiWeb management GUI.



A FortiWeb administrator needs to protect new API endpoints that a development team is publishing.
To secure these API endpoints, which three configuration actions should the administrator perform on FortiWeb? (Choose three.)

  1. Configure Active Directory (AD) single sign-on (SSO) for the web portal.
  2. Apply API schema validation to incoming requests.
  3. Enable machine learning (ML)-based API protection.
  4. Enforce API user key requirements in the API policy.
  5. Activate SAML authentication for general user access.

Answer(s): B,C,D

Explanation:

API schema validation verifies that incoming API requests match the expected structure, parameters, and data types. ML-based API protection helps FortiWeb learn normal API behavior and detect abnormal or suspicious API requests. API user key enforcement ensures that only authorized API clients can access the protected endpoints.



Viewing page 4 of 11
Viewing questions 16 - 20 out of 50 questions


Post your Comments and Discuss Fortinet NSE5_FWB_AD-8.0 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!