NSE6_FWB-6.4 Fortinet NSE 6 - FortiWeb 6.4 Questions and Answers

Determines whether an anomaly is a real attack or just a benign anomaly that should be ignored

Builds a threat model behind every parameter and HTTP method

Determines if a detected threat is a false-positive or not

Determines whether traffic is an anomaly, based on observed application traffic over time

Automatically identifies and blocks suspicious IPs

FortiWeb scans all traffic without taking action and makes recommendations on rules

Automatically builds rules sets

Automatically blocks all detected threats

Enable “Shared IP” and configure the separate rate limits for requests from NATted source IPs.

Configure FortiWeb to use “X-Forwarded-For:” headers to find each client’s private network IP, and to block attacks using that.

Enable SYN cookies.

Configure a server policy that matches requests from shared Internet connections.

For SNI, you select the certificate that FortiWeb will present in the server pool, not in the server policy.

After enabling HSTS, redirects to HTTPS are no longer necessary.

In true transparent mode, the TLS session terminator is a protected web server.

Enabling RC4 protects against the BEAST attack, but is not recommended if you configure FortiWeb to only offer TLS 1.2.

In transparent inspection mode, you select which certificate that FortiWeb will present in the server pool, not in the server policy.

FortiGate should forward web traffic to the server pool IP addresses.

The configuration is incorrect. FortiWeb should always be located upstream to FortiGate.

You must disable the Preserve Client IP setting on FotriGate for this configuration to work.

FortiGate should forward web traffic to virtual server IP address.