Refer to the exhibit.You are deploying FortiWeb to handle HTTPS traffic from clients and forward cleartext traffic to a back-end server.You want FortiWeb to decrypt the HTTPS session, inspect the traffic, and then send the traffic to the server using HTTP.What can you configure on FortiWeb to make this behavior happen?
Answer(s): D
SSL offloading allows FortiWeb to terminate the client HTTPS connection, decrypt and inspect the traffic, and then forward the request to the back-end server over HTTP. This provides inspection while removing the SSL processing requirement from the server.
A user from group B sends 150 requests in one minute to this endpoint:Group B users are allowed access to only /api/v1/reports and are limited to 50 requests per minute.What should the FortiWeb administrator configure to stop this abuse?
Answer(s): B
Group-based rate limiting enforces the allowed request threshold for group B users, limiting them to 50 requests per minute and preventing excessive API use even when the request includes a valid API key.
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?
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?
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?
Answer(s): A
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?
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.)
Answer(s): B,C,D
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.
FortiWeb is blocking groups of users behind your load balancer. In the logs, all users show the same source IP address.Which action should you take to restore proper client identification?
When traffic passes through a load balancer, FortiWeb may see only the load balancer IP as the source. Inserting the original client IP address in an HTTP header, such as X-Forwarded-For, allows FortiWeb to identify individual clients correctly and avoid applying IP-based blocking to an entire group of users.
Share your comments for Fortinet NSE5_FWB_AD-8.0 exam with other users:
very helpful!
question #18s answer should be a, not d. this should be corrected. it should be minvalidityperiod
thanks for the exact solution
need to refer the questions and have to give the exam
i need it right now if it was possible please
i need it very much please share it in the fastest time.
correct answer is d for student.java program
q:37 c is correct
q6 exam topic: terramearth, c: correct answer: copy 1petabyte to encrypted usb device ???
explained answers
plan to take theaws certified developer - associate dva-c02 in the next few weeks
very helpfull
good questions
help to practice csa exam
nice tip and well documented
i need the exam
please upload
prepping for fsc exam
pd1 with great experience
@t it seems like azure service bus message quesues could be the best solution
helpful to check your understanding.
question 128 the answer should be static not auto
more comments here
great support to appear for exams
useful dumps
making progress
q31 answer should be d i think
is this real?
q10: c and f are also true. q11: this is outdated. you no longer need ownership on a pipe to operate it
good questions with simple explanation
admin guide (windows) respond to malicious causality chains. when the cortex xdr agent identifies a remote network connection that attempts to perform malicious activity—such as encrypting endpoint files—the agent can automatically block the ip address to close all existing communication and block new connections from this ip address to the endpoint. when cortex xdrblocks an ip address per endpoint, that address remains blocked throughout all agent profiles and policies, including any host-firewall policy rules. you can view the list of all blocked ip addresses per endpoint from the action center, as well as unblock them to re-enable communication as appropriate. this module is supported with cortex xdr agent 7.3.0 and later. select the action mode to take when the cortex xdr agent detects remote malicious causality chains: enabled (default)—terminate connection and block ip address of the remote connection. disabled—do not block remote ip addresses. to allow specific and known s
very inciting
question 5, it seems a instead of d, because: - care plan = case - patient = person account - product = product2;
it look like real one
Keeping this site free takes real effort. We constantly battle automated scraping and unauthorized content copying. A quick account helps us protect the community and keep the site free.
To continue studying for your NSE5_FWB_AD-8.0, please sign in or create a free account.