Airlock as a Service Knowledge Base

Deny rule exceptions

The Deny rule exceptions page allows you to configure exceptions to built-in deny rules for the selected tenant. Use these exceptions to prevent legitimate requests or specific request data from being blocked by rules that detect known attack patterns.

Exceptions can be restricted to specific application modules, deny rule keys, request data, and optional request conditions.

Deny rule exceptions

The Deny rule exceptions table lists the configured exceptions for the selected tenant.

For each exception, the table shows:

  • Module – application module to which the exception applies.

  • Blocked data – type of request data and matching criteria for which the exception is defined.

  • Conditions – request conditions that determine when the exception applies.

  • Rule keys – built-in deny rules to which the exception applies.

Use the Module filter to narrow down the displayed exceptions.

Use the menu icon (⋮) of an existing exception to access its available actions.

Add a deny rule exception

  1. Click ⨁ Add exception.

    ➔ The Add deny rule exception dialog opens.

  2. Configure the following settings:

    • Module: Select the application module to which the exception applies:

      • Loginapp

      • Adminapp

      • Transaction approval

    • Rule keys: Select one or more built-in deny rule keys to which the exception applies, for example, SQL, XSS, or SSRF. You can select multiple rule keys or all available keys. Leave the field empty to apply the exception to all built-in deny rules.

  3. Under Blocked data, select the data type for which the exception is defined and configure the corresponding matching criteria as described below.

Blocked data

Under Data type, select one of the following options.

Parameter

Select Parameter to define an exception for request parameters.

Under Matching criteria, select Name, Value, or both, and optionally restrict the match to a specific parameter source:

  • Name:

    • Under Parameter name, select a matching operator and enter the parameter name to match.

    • Use the Aa button to switch between case-sensitive and case-insensitive matching.

  • Value:

    • Under Parameter value, select a matching operator and enter the parameter value to match.

    • Use the Aa button to switch between case-sensitive and case-insensitive matching.

  • Source: Select the origin of the parameter:

    • Any: Match parameters regardless of their source.

    • POST: Match parameters from the POST request body.

    • Query: Match parameters from the query string of the request URL.

The following matching operators are available:

  • equals: Matches the specified string exactly.

  • starts with: Matches strings that begin with the specified string.

  • ends with: Matches strings that end with the specified string.

  • contains: Matches strings containing the specified string.

  • matches regex: Matches strings against the specified regex.

Header

Select Header to define an exception for HTTP request headers.

Under Matching criteria, select Name, Value, or both:

  • Name:
    Under Header name, select a matching operator* and enter the header name to match.

  • Value:
    Under Header name, select a matching operator* and enter the header value to match. Use the Aa button to switch between case-sensitive and case-insensitive matching.

* For descriptions of the available matching operators, see Parameter.

Path

Select Path to define an exception based on the request path.

Under Matching path, select a matching operator* and enter the request path to match.

Use the Aa button to switch between case-sensitive and case-insensitive matching.

* For descriptions of the available matching operators, see Parameter.

Path segment

Select Path segment to define an exception for a specific segment of the request path.

Under Matching criteria, select Segment, Value, or both:

  • Segment:
    Under Segment index, enter the position of the segment within the request path. Indexing starts at 0.

  • Value:
    Under Segment value, select a matching operator* and enter the segment value to match. Use the Aa button to switch between case-sensitive and case-insensitive matching.

* For descriptions of the available matching operators, see Parameter.

JSON field

Select JSON field to define an exception for JSON data in the request body.

Under Matching criteria, configure the following settings:

  • JSON path: Optionally enter a JSONPath expression identifying the field within the request body, for example, $.user.name. Leave the field empty to match based on the key or value alone. JSONPath filter expressions are not supported.

  • Key: Select a matching operator* and enter the JSON key to match. Use the Aa button to switch between case-sensitive and case-insensitive matching.

  • Value: Select a matching operator* and enter the JSON value to match. Use the Aa button to switch between case-sensitive and case-insensitive matching.

Key and Value cannot be combined. However, either criterion can be combined with JSON path.

* For descriptions of the available matching operators, see Parameter.

GraphQL

Select GraphQL to define an exception for GraphQL request data.

Under Matching criteria, select and configure one or more of the following properties:

  • Field:
    Under Field name, select a matching operator* and enter the GraphQL field name to match.

  • Argument:
    Under Argument name, select a matching operator* and enter the argument name to match.

  • Value:
    Under Argument value, select a matching operator* and enter the argument value to match.

Use the Aa button next to each input field to switch between case-sensitive and case-insensitive matching.

The criteria can be combined to restrict the exception to specific GraphQL fields, arguments, or values.

* For descriptions of the available matching operators, see Parameter.

Any data

Select Any data to define an exception without restricting it to specific blocked request data.

No additional data-matching settings are available for this option.

Conditions must be configured when Any data is selected to restrict the requests to which the exception applies.

* For descriptions of the available matching operators, see Parameter.

Conditions

By default, a deny rule exception applies to every request that matches its configured exception criteria.

To restrict the exception to specific requests:

  1. Select Set conditions to requests.

  2. Under Apply condition to, select how the configured conditions are evaluated:

    • Matching requests: Apply the exception to requests that meet every configured condition.

    • Not matching requests: Apply the exception to requests that do not meet at least one configured condition.

  3. Under Condition options, select and configure one or more of the following conditions:

    • Methods:
      Under Matching methods, select the HTTP request methods to match.

    • Path:
      Under Matching path, select a matching operator* and enter the request path to match. Use the Aa button to switch between case-sensitive and case-insensitive matching.

    • Media type:
      Under Matching media type, select a matching operator* and enter the request's media type to match, for example, application/json.

    • Header: Configure the following properties to match HTTP request headers:

      • Header name: Select a matching operator* and enter the header name to match. Leave the field empty to match any header whose value matches the configured value condition.

      • Header value: Select a matching operator* and enter the header value to match. Leave the field empty to match the header by name only. Use the Aa button to switch between case-sensitive and case-insensitive matching.

    • Remote IP:

      • Under Apply condition to, select how the configured IP ranges are evaluated:

        • Matching remote IPs: Match requests originating from IP addresses within the specified CIDR ranges.

        • Not matching remote IPs: Match requests originating from IP addresses outside the specified CIDR ranges.

      • Under CIDR ranges, enter the IP address ranges in CIDR notation, for example, 192.0.2.0/24. Click Add CIDR range to specify additional ranges. Use the delete icon next to a range to remove it.

If no conditions are configured, the exception applies to every request that matches its blocked-data criteria. The Any data option requires conditions.

* For descriptions of the available matching operators, see Parameter.

Save the exception

After configuring the blocked data and any applicable conditions, click Save.

The new exception is added to the Deny rule exceptions table.

Manage existing deny rule exceptions

Use the menu icon (⋮) of an exception in the Deny rule exceptions table to manage it.

The following actions are available:

  • Edit exception: Modify the configuration of an existing exception. Save your changes when finished.

  • Duplicate exception: Create a copy of an existing exception.

  • Delete exception: Remove an exception that is no longer required.