What if you want to allow a web crawler, but only if it is not too demanding, and comes from a source IP that is known to be legitimate for that crawler? What if you want to allow only a client that is a senior manager’s IP, and only if it hasn’t been infected by malware whose access rate is contributing to a DoS?
Advanced access control rules provide a degree of flexibility for these types of complex conditions. You can combine any or all of these criteria:
- Source IP
- Rate limit (including rate limiting for specific types of content)
- HTTP header or response code
- Predefined or custom attack or data leak signature violation
- Transaction or packet interval timeout
- Real browser enforcement
- CAPTCHA enforcement
You use the rule's filters to specify all criteria that you require allowed traffic to match.
The filters apply to request traffic only, with the following exceptions:
- HTTP Response Code and Content Type apply to responses.
- Signature Violation applies to either requests or responses, depending on which signatures you enable.
FortiWeb includes predefined rules that defend against some popular attacks. You cannot edit these predefined rules, but you can view their settings or create duplicates of them that you can edit (that is, by cloning).
|Advanced access control is available even if FortiWeb derives client source IP addresses from the X-header field. For details, see Defining your proxies, clients, & X-headers.|
- Go to Web Protection > Advanced Protection > Custom Policy, and select the Custom Rule tab.
To access this part of the web UI, your administrator’s account access profile must have Read and Write permission to items in the Web Protection Configuration category. For details, see Permissions.
- Do one of the following:
- To create a new rule, click Create New.
- To create a new rule based on a predefined rule, select the predefined rule to use, and then click Clone.
|Name||Type a unique name that can be referenced in other parts of the configuration. The maximum length is 63 characters.|
Select which action the FortiWeb appliance will take when it detects a violation of the rule:
The default value is Alert.
Caution: This setting is ignored when Monitor Mode is enabled.
Type the number of seconds that you want to block subsequent requests from the client after the FortiWeb appliance detects that the client has violated the rule.
When rule violations are recorded in the attack log, each log message contains a Severity Level (
The default value is Medium.
|Trigger Action||Select which trigger, if any, that the FortiWeb appliance will use when it logs and/or sends an alert email about a violation of the rule. For details, see Viewing log messages.|
Enter the maximum amount of time (in seconds) that FortiWeb waits for results from the client.
Available only when the Verification Method is Real Browser Enforcement or CAPTCHA Enforcement.
|Max Attempt Times||
If CAPTCHA Enforcement is selected for Verification Method, enter the maximum number of attempts that a client may attempt to fulfill a CAPTCHA request.
For Mobile Client App
Available only when Mobile Application Identification is enabled in System > Config > Feature Visibility.
The Filter Type value determines which settings are displayed in the next dialog box.
Source IPv4/IPv6/IP Range—Type the IP address of a client that is allowed. Depending on your configuration of how FortiWeb derives the client’s IP, this may be the IP address that is indicated in an HTTP header rather than the IP header. For details, see Defining your proxies, clients, & X-headers.
To enter an address range, enter the first and last address in the range separated by a hyphen. For example, for an IPv4 address, enter
192.0.2.1 – 192.0.2.155. For an IPv6 address, enter
For Meet this condition if, select one of the following:
Source IP matches—The request will match the condition if it contains the Source IPv4/IPv6/IP Range value.
Source IP does not match—The request will match the condition if it doesn't contain the Source IPv4/IPv6/IP Range value.
User—Enter a user name to match, and then specify whether the condition matches if the request contains the specified user name or matches only for user names other than the specified one.
Note: This type of filter requires you to select a user tracking policy in any protection profile that uses this advanced access policy. For details, see Tracking users.
URL—Type a regular expression that matches one or more URLs, such as
/index\.jsp. Do not include the host name.
To accept requests that do not match the URL, do not precede the URL with an exclamation mark (
HTTP Header—Indicate a single HTTP Header Name such as
Host:, and all or part of its value in Header Value. The request matches the condition if that header matches the exact name or value, or matches your regular expression (depending on whether you have selected Simple String or Regular Expression). Value matching is case sensitive and supports null value match.
If you select Header Value Reverse Match, the request matches the condition if the header does not contain the exact value or regular expression.
Optionally, enable HTTP Method Check and configure a simple string or regular expression for the HTTP method that FortiWeb will search for in the header field. When you enable HTTP Method Check, you can also enable HTTP Method Reverse Match so that the request matches the condition if the header does not contain the HTTP method's exact value or regular expression.
To prevent accidental matches, specify as much of the header’s value as possible. Do not use an ambiguous substring.
For example, entering the value
Access Rate Limit—This is the number of requests per second per client IP. Depending on your configuration of how FortiWeb will derive the client’s IP, this may be the IP address that is indicated in an HTTP header rather than the IP header. For details, see Defining your proxies, clients, & X-headers.
You can add only one Access Rate Limit filter to each rule.
Signature Violation—Matches if FortiWeb detects a selected category of attack signature in the request or response. The following categories are available:
- Cross Site Scripting
- Cross Site Scripting (Extended)
- SQL Injection
- SQL Injection (Extended)
- SQL Injection (Syntax Based Detection)
- Generic Attacks
- Generic Attacks (Extended)
- Known Exploits
- Custom Signature (group or individual rule)
- Geo IP—Choose the countries to match. If you select Yes, FortiWeb matches the traffic from all countries except the ones you select. If you select No, FortiWeb matches the traffic from the countries you select.
To use one of these categories in an advanced access control rule, enable the corresponding item in your signatures configuration. For details, see Blocking known attacks & data leaks.
- Transaction Timeout—Matches if the lifetime of a HTTP transaction exceeds the transaction timeout you specify. Specify a timeout value of 1 to 3600 seconds.
HTTP Response Code—Matches if a HTTP response code matches a code or range of codes that you specify. For example,
500-503. To specify more than one response code or range, create additional HTTP Response Code filters.
- Content Type—Matches an HTTP response for a file that matches one of the specified types. Use with Occurrence to detect and control web scraping (content scraping) activity.
- Packet Interval Timeout—Matches if the time period between packets arriving from either the client or server (request or response packets) exceeds the value in seconds you specify for Packet Timeout Interval. Enter a value from 1 to 60.
- Time Period—Matches if the time period of a request matches that you specify. You can set a daily period or fixed period.
Occurrence—Matches if a transaction matches other filter types in the current rule at a rate that exceeds a threshold you specify.
- To measure the rate by counting source client IP address, for Traced By, select Source IP.
- To measure by HTTP session, select HTTP Session.
Note: The HTTP Session option requires that you enable the Session Management option in your protection profile. For details, see Configuring a protection profile for inline topologies.
To measure by client, select User.
Note: The User option requires that you enable User Tracking in your protection profile. For details, see Configuring a protection profile for inline topologies.
For example, you can require both a matching request URL, HTTP header, and client source IP in order to allow a request.
You can add only one Access Rate Limit filter to each rule.
For example, to create a policy that allows rate-limited access by 3 client IPs, you would group the corresponding 3 advanced access rules for each of those IPs into the policy. In Priority, enter the priority for each rule in relation to other defined rules. Rules with lower numbers (higher priority) are applied first.
Attack log messages contain
Custom Access Violation when this feature detects an unauthorized access attempt.