Discuss with expertTry it for free
© 2026 Direct Cursus Technology L.L.C.

Editing a WAF exclusion rule

Written by
Updated at July 20, 2026
View in Markdown
  1. In the management console, select the folder containing the WAF profile.
  2. Navigate to Smart Web Security.
  3. In the left-hand panel, select WAF profiles.
  4. Select the profile where you want to edit an exclusion rule.
  5. In the left-hand menu, go to the Exclusion rules tab.
  6. In the rule row, click and select Edit. In the window that opens:

    1. Edit the exclusion rule name and description as needed.

    2. Optionally, enable Write logs to log exception rule triggering.

    3. In the Skip checks field, select:

      • All rules: Exclusion will apply to all rules.
      • Selected rules: Exclusion will apply to selected rules. Click Add rules to select rules.

    4. Under Scope, select:

      • Entire request: Exception will apply to entire HTTP request.

      • Request part: Exception will apply only to the request part specified in the parameters. The rest of the request will be checked according to the WAF profile settings.

        In the Exception parameters field, select one or more of the following: HTTP body, Cookie, HTTP header, or Query params. Set a value for each parameter. Enable Case sensitive as needed.

        To add one more value for a parameter, click or.

    5. Under Traffic conditions, specify the traffic the rule will apply to:

      • All traffic: Rule will apply to all traffic.

      • On condition: Rule will apply to the traffic defined in the Conditions field:

        • IP: IP address, IP address range, or IP address region.
        • HTTP header: HTTP header string.
        • Request URI: Request path.
        • Host: Domain receiving the request.
        • HTTP method: Request method.
        • Cookie: Cookie header string.
        • Bot name: Names of legitimate bots owned by various companies and services.
        • Bot category: Verified bot categories based on their purpose or nature of action.
        • Verified bot: Filtering based on whether the bot is verified (yes or no).
        • Bot score: Filtering based on request bot score, from 0 (the lowest, represents a human) to 100 (the highest, represents a bot).
        • FingerPrint: SSL/TLS connection fingerprint.

        You can set multiple conditions of the same type by selecting all the condition types you need in the Conditions field.

        You can also set multiple conditions of the same type at the same time by clicking and or or in the section with the condition you need.

        To delete a condition, click .

    6. Click Save.

With Terraform, you can quickly create a cloud infrastructure in Yandex Cloud and manage it using configuration files. These files store the infrastructure description written in HashiCorp Configuration Language (HCL). If you change the configuration files, Terraform automatically detects which part of your configuration is already deployed, and what should be added or removed.

Terraform is distributed under the Business Source License. The Yandex Cloud provider for Terraform is distributed under the MPL-2.0 license.

For more information about the provider resources, see the guides on the Terraform website or its mirror.

If you do not have Terraform yet, install it and configure the Yandex Cloud provider.

To manage infrastructure using Terraform under a service account or user accounts (a Yandex account, a federated account, or a local user), authenticate using the appropriate method.

  1. Open the Terraform configuration file and edit the exclusion_rule section in the yandex_sws_waf_profile description.

    # WAF profile
resource "yandex_sws_waf_profile" "default" {
  name = "waf-profile-default"
  core_rule_set {
    inbound_anomaly_score = 2
    paranoia_level        = local.waf_paranoia_level
    rule_set {
      name    = "OWASP Core Ruleset"
      version = "4.0.0"
    }
  }

  ...

  # Exclusion rule
  exclusion_rule {
    name = "<exclusion_rule_name>"
    condition {
      source_ip {
        ip_ranges_match {
          ip_ranges = [
            "<IP_address_range_1>",
            "<IP_address_range_2>",
            ...
            "<IP_address_range_n>"
          ]
        }
        ip_ranges_not_match {
          ip_ranges = [
            "<IP_address_range_3>",
            "<IP_address_range_4>",
            ...
            "<IP_address_range_y>"
          ]
        }
      }
    }

    exclude_rules {
      exclude_all = <true_or_false>
      rule_ids    = [
        "rule_ID_1",
        "rule_ID_2",
        ...
        "rule_ID_n",
      ]
    }
  }
}

    For more on the properties of the sws_waf_profile resource, see this provider guide.

  2. Apply the changes:

    1. In the terminal, navigate to the configuration file directory.

    2. Make sure the configuration is correct using this command:

      terraform validate

      If the configuration is valid, you will get this message:

      Success! The configuration is valid.

    3. Run this command:

      terraform plan

      You will see a list of resources and their properties. No changes will be made at this step. Terraform will show any errors in the configuration.

    4. Apply the configuration changes:

      terraform apply

    5. Type yes and press Enter to confirm the changes.

You can check the resource update in the management console.

Use the update REST API method for the WafProfile resource or the WafProfile/Update gRPC API call.

Useful links

Previous
Adding an exclusion rule
Next
Deleting an exclusion rule