Este conteúdo foi traduzido por máquina para sua conveniência e a Huawei Cloud não pode garantir que o conteúdo foi traduzido com precisão. Para exibir o conteúdo original, use o link no canto superior direito para mudar para a página em inglês.
Central de ajuda/ Web Application Firewall/ Guia de usuário/ Configuração da regra/ Configuring a Global Protection Whitelist (Formerly False Alarm Masking) Rule
Atualizado em 2022-11-02 GMT+08:00

Configuring a Global Protection Whitelist (Formerly False Alarm Masking) Rule

When WAF detects a malicious attack that matches the basic web protection rule or custom rules you configure, it processes the attack event based on the protective action in the hit rule.

You can add false alarm masking rules to let WAF ignore certain rule IDs or event types (for example, skip XSS checks for a specific URL).

  • If you select All protection for Ignore WAF Protection, all WAF rules do not take effect, and WAF allows all request traffic to the domain names in the rule.
  • If you select Basic Web Protection for Ignore WAF Protection, you can ignore basic web protection by rule ID, attack type, or all built-in rules. For example, if XSS check is not required for a URL, you can whitelist XSS rule.

Se você ativou projetos corporativos, verifique se tem todas as permissões de operação para o projeto em que sua instância do WAF está localizada. Em seguida, você pode selecionar o projeto na lista suspensa Enterprise Project e configurar políticas de proteção para os nomes de domínio no projeto.

Prerequisites

A website has been added to WAF.

Constraints

  • If you select All protection for Ignore WAF Protection, all WAF rules do not take effect, and WAF allows all request traffic to the domain names in the rule.
  • If you select Basic web protection for Ignore WAF Protection, global protection whitelist (formerly false alarm masking) rules take effect only for events triggered against WAF built-in rules in Basic Web Protection and anti-crawler rules under Feature Library.
    • Basic web protection rules

      Basic web protection defends against common web attacks, such as SQL injection, XSS attacks, remote buffer overflow attacks, file inclusion, Bash vulnerability exploits, remote command execution, directory traversal, sensitive file access, and command and code injections. Basic web protection also detects web shells and evasion attacks.

    • Feature-based anti-crawler protection

      Feature-based anti-crawler identifies and blocks crawler behavior from search engines, scanners, script tools, and other crawlers.

  • Leva vários minutos para que uma nova regra entre em vigor. Depois que a regra entrar em vigor, os eventos de proteção desencadeados pela regra serão exibidos na página Events.
  • You can configure a global whitelist (formerly false alarm masking) rule by referring to Manipulação de alarmes falsos. After handling a false alarm, you can view the rule in the global whitelist (formerly false alarm masking) rule list.
  • Currently, the following regions support global protection whitelist (formerly false alarm masking) rules:
    • CN-Hong Kong
    • AP-Bangkok
    • AP-Singapore
    • RU-Moscow201

Procedure

  1. Efetue login no console de gerenciamento.
  2. Clique em no canto superior esquerdo do console de gerenciamento e selecione uma região ou projeto.
  3. Clique em no canto superior esquerdo e escolha Web Application Firewall em Security & Compliance.
  4. No painel de navegação, escolha Website Settings.
  5. Na coluna Policy da linha que contém o nome de domínio, clique em Configure Policy.
  6. In the Global Protection Whitelist (Formerly False Alarm Masking) configuration area, click Status if needed. Then, click Customize Rule.

    Figura 1 Global Protection Whitelist configuration area

  7. In the upper left corner of the Global Protection Whitelist page, click Add Rule.
  8. Add a global whitelist rule by referring to Tabela 1. Figura 2 shows an example.

    Figura 2 Add Global Protection Whitelist Rule

    Tabela 1 Parameters

    Parameter

    Description

    Example Value

    Scope

    • All domain names: By default, this rule will be used to all domain names that are protected by the current policy.
    • Specified domain names: This rule will be used to the specified domain names that match the wildcard domain name being protected by the current policy.

    Specified domain names

    Domain Name

    This parameter is mandatory when you select Specified domain names for Scope.

    Enter a single domain name that matches the wildcard domain name being protected by the current policy.

    www.example.com

    Condition List

    Click Add to add conditions. At least one condition needs to be added. You can add up to 30 conditions to a protection rule. If more than one condition is added, all of the conditions must be met for the rule to be applied. A condition includes the following parameters:

    Parameters for configuring a condition are described as follows:
    • Field
    • Subfield: Configure this field only when Params, Cookie, or Header is selected for Field.
      AVISO:

      The length of a subfield cannot exceed 2,048 bytes. Only digits, letters, underscores (_), and hyphens (-) are allowed.

    • Logic: Select a logical relationship from the drop-down list.
    • Content: Enter or select the content that matches the condition.

    Path, Include, /product

    Ignore WAF Protection

    • All protection: All WAF rules do not take effect, and WAF allows all request traffic to the domain names in the rule.
    • Basic Web Protection: You can ignore basic web protection by rule ID, attack type, or all built-in rules. For example, if XSS check is not required for a URL, you can whitelist XSS rule.

    Basic Web Protection

    Ignored Protection Type

    If you select Basic web protection for Ignored Protection Type, specify the following parameters:

    • ID: Configure the rule by event ID.
    • Attack type: Configure the rule by attack type, such as XSS and SQL injection. One type contains one or more rule IDs.
    • All built-in rules: all checks enabled in Basic Web Protection.

    Attack type

    ID

    This parameter is mandatory when your select ID for Ignored Protection Type.

    ID of an attack event on the Events page. If the event type is Custom, it has no event ID. Click Handle False Alarm in the row containing the attack event to obtain the ID. You are advised to configure global protection whitelist (formerly false alarm masking) rules on the the Events page by referring to Manipulação de alarmes falsos.

    041046

    Attack type

    This parameter is mandatory when your select Attack type forIgnored Protection Type.

    Select an attack type from the drop-down list box.

    WAF can defend against XSS attacks, web shells, SQL injection attacks, malicious crawlers, remote file inclusions, local file inclusions, command injection attacks, and other attacks.

    SQL injection

    Rule Description

    A brief description of the rule. This parameter is optional.

    SQL injection attacks are not intercepted.

    Advanced Settings

    To ignore attacks of a specific field, specify the field in the Advanced Settings area. After you add the rule, WAF will stop blocking attack events of the specified field.

    Select a target field from the first drop-down list box on the left. The following fields are supported: Params, Cookie, Header, Body, and Multipart.
    • If you select Params, Cookie, or Header, you can select All or Specified field to configure a subfield.
    • If you select Body or Multipart, you can select All.
    • If you select Cookie, the Domain Name and Path can be empty.
    NOTA:

    If All is selected, WAF will not block all attack events of the selected field.

    Params

    All

  9. Click OK.

    Figura 3 Global protection whitelist (formerly false alarm masking) rules

Other Operations

  • Para desativar uma regra, clique em Disable na coluna Operation da regra. O Rule Status padrão é Enabled.
  • To modify a global protection whitelist (formerly false alarm masking) rule, click Modify in the row containing the rule.
  • To delete a global protection whitelist (formerly false alarm masking) rule, click Delete in the row containing the rule.