Enable to track a client by the inserted cookie, or source IP when cookie is prohibited.
For details, see Client management.

Select the Threat Score Profile so that FortiWeb can take action on IPs or clients when their threat score accumulates to a certain value.

If you leave it blank, the system will use the Global Configuration in Client Management.

This option is available only when Client Management is enabled.

Select the name of the signature set you have configured in Web Protection > Known Attacks, if any, that will be applied to matching requests.

Enable AMF3, XML, or JSON Protocol Detection if applicable.

Attack log messages for this feature vary by which type of attack was detected. For a list, see Blocking known attacks .

Select the name of an HTTP parameter constraint, if any, that will be applied to matching requests. For details, see HTTP/HTTPS protocol constraints.

Attack log messages for this feature vary by which type of constraint was violated.

Select the X-Forwarded-For: and X-Real-IP: HTTP header settings to use, if any. For details, see Defining your proxies, clients, & X-headers.

Note: Configuring this option is required if the true IP address of the client is hidden from FortiWeb because a load balancer or other web proxy is deployed in front. In that case, you must configure an X-header rule so that FortiWeb will block only requests related to the original client. Otherwise, it may block all requests whenever any attack occurs, since all requests will appear to originate from the proxy’s IP.

Select the name of a combination source IP, rate limit, HTTP header, and URL access policy, if any, that will be applied to matching requests. For details, see Custom Policy.

Attack log messages contain Custom Access Violation when this feature detects a violation.

Select the name of padding oracle protection rule, if any, that will be applied to matching requests. For details, see Defeating cipher padding attacks on individually encrypted inputs.

Attack log messages contain Padding Oracle Attack when this feature detects a violation.

Select the name of cross-site request forgery protection rule, if any, to apply to matching requests. For details, see Defeating cross-site request forgery (CSRF) attacks.

Available only when Session Management is selected.

Select the name of HTTP header security policy, if any, to apply to matching responses.

For details, see HTTP Security Headers.

Select the name of an MiTB protection rule, if any, that will be applied to matching requests. For details, see Protection for Man-in-the-Browser (MiTB) attacks.

Select the name of a URL encryption policy if any, that will be applied to matching requests. For details, see URL encryption.

Select the name of a SQL/XSS syntax based detection policy if any, that will be applied to matching requests. For details, see Syntax-based SQL/XSS injection detection.

Select the name of the parameter validation rule, if any, that will be applied to matching requests. For details, see Validating parameters (“input rules”).

Attack log messages contain Parameter Validation Violation when this feature detects a parameter rule violation.

Select the name of the hidden fields protection rule, if any, to use to protect hidden fields on your website. For details, see Preventing tampering with hidden inputs.

Attack log messages contain Hidden Field Manipulation when this feature detects tampering.

This option appears only when Session Management is enabled.

Select an existing file security policy, if any, that will be applied to matching HTTP requests. For details, see Limiting file uploads.

Attack log messages contain Illegal File Size when this feature detects an excessively large upload.

Enable to scan requests that use action message format 3.0 (AMF3) for:

• Cross-site scripting (XSS) attacks
• SQL injection attacks
• Common exploits

and other attack signatures that you have enabled in Signatures.

AMF3 is a binary format that can be used by Adobe Flash/Flex clients to send input to server-side software.

Caution: To scan for attacks or enforce input rules on AMF3, you must enable this option. Failure to enable the option will cause the FortiWeb appliance to be unable to scan AMF3 requests for attacks.

Select the name of a WebSocket security rule, if any, that will be applied to matching requests. For details, see WebSocket protocol.

Select the name of a gRPC security rule, if any, that will be applied to matching requests. For details, see gRPC protocol.

Select the name of the URL access policy, if any, that will be applied to matching HTTP requests. For details, see Restricting access based on specific URLs.

Attack log messages contain URL Access Violation when this feature detects a URL matched by this policy.

Select an existing allow method policy, if any, that will be applied to matching HTTP requests. For details, see Specifying allowed HTTP methods.

Attack log messages contain HTTP Method Violation when this feature detects a non-allowed HTTP request method.

Select the name of an existing bot mitigation policy. For details, see Configuring bot mitigation policy.

Enable to configure the JWT token secret and token header to verify a request from a mobile application.

Refer to Approov doc for how to get the token.

For details, see Configuring mobile API protection.

Note: You need to enable Mobile Application Identification first from System > Config > Feature Visibility.

Enter the token secret that you have got from Approov.

Available only when Mobile Application Identification is enabled.

Specify the header where the token is carried.

Available only when Mobile Application Identification is enabled.

Select the name of an existing API protection policy. For details, see Configuring mobile API protection.

Select the name of a URL rewriting rule set, if any, that will be applied to matching requests.

For details, see Rewriting & redirecting.

Select the name of an authorization policy, if any, that will be applied to matching requests. For details, see Offloading HTTP authentication & authorization.

If the client fails to authenticate, it will receive an HTTP 403 Access Forbidden error message.

Enable to detect source IP addresses that a FortiGate unit is currently preventing from interacting with the network and protected systems. Then, select the action that FortiWeb takes if it detects a quarantined IP address:

• Alert—Accept the request and generate an alert email, log message, or both.
• Alert & Deny—Block the request and generate an alert, log message, or both.
• Deny (no log)—Block the request (or reset the connection).

Note: If FortiWeb is deployed behind a NAT load balancer and this option is enabled, to prevent FortiWeb from blocking all connections when it detects a violation of this type, define an X-header that indicates the original client’s IP. For details, see Defining your proxies, clients, & X-headers.

In addition, select a severity level and trigger policy.

For information on configuring communication with the FortiGate that provides the list of quarantined IP addresses, see Receiving quarantined source IP addresses from FortiGate.

Type a URL including the FQDN/IP and path, if any, to which a client will be redirected if:

• Its request violates any of the rules in this profile, and
• The Action for the rule is set to Redirect.

For example, you could enter:

www.example.com/products/

If you do not enter a URL, depending on the type of violation and the configuration, the FortiWeb appliance will log the violation, may attempt to remove the offending parts, and could either reset the connection or return an HTTP 403 Access Forbidden or 404 File Not Found error message.