Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive

Handling False Alarms

Updated on 2025-01-17 GMT+08:00

If you confirm that an attack event on the Events page is a false alarm, you can handle the event as false alarm by ignoring the URL and rule ID in basic web protection, or by deleting or disabling the corresponding protection rule you configured. You can also add the attack source IP addresses to a whitelist or blacklist to handle the false alarm. After an attack event is handled as a false alarm, the event will not be displayed on the Events page anymore. You will no longer receive any alarm notifications about the events of this kind.

WAF detects attacks by using built-in basic web protection rules, built-in features in anti-crawler protection, and custom rules you configured (such as CC attack protection, precise access protection, blacklist, whitelist, and geolocation access control rules). WAF will respond to detected attacks based on the protective actions (such as Block and Log only) defined in the rules and display attack events on the Events page.

NOTE:

If you have enabled enterprise projects, ensure that you have all operation permissions for the project where your WAF instance locates. Then, you can select the project from the Enterprise Project drop-down list and handle false alarms in the project.

Prerequisites

There is at least one false alarm event in the event list.

Constraints

  • Only attack events blocked or recorded by built-in basic web protection rules and features in anti-crawler protection can be handled as false alarms.
  • For events generated based on custom rules (such as a CC attack protection rule, precise protection rule, blacklist rule, whitelist rule, or geolocation access control rule), they cannot be handled as false alarms. To ignore such an event, delete or disable the custom rule hit by the event.
  • An attack event can only be handled as a false alarm once.
  • After an attack event is handled as a false alarm, the attack event will not be displayed on the Events page. You will no longer receive any alarm notifications about the events of this kind.
  • Dedicated WAF instances earlier than June 2022 do not support All protection for Ignore WAF Protection. Only Basic web protection can be selected.

Application Scenarios

Sometimes normal service requests may be blocked by WAF. For example, suppose you deploy a web application on an ECS and then add the public domain name associated with that application to WAF. If you enable basic web protection for that application, WAF may block the access requests that match the basic web protection rules. As a result, the website cannot be accessed through its domain name. However, the website can still be accessed through the IP address. In this case, you can handle the false alarms to allow normal access requests to the application.

Handling False Alarms

  1. Log in to the management console.
  2. Click in the upper left corner of the management console and select a region or project.
  3. Click in the upper left corner and choose Web Application Firewall under Security & Compliance.
  4. In the navigation pane on the left, choose Events.
  5. Click the Search tab. In the website or instance drop-down list, select a website to view corresponding event logs. The query time can be Yesterday, Today, Past 3 days, Past 7 days, Past 30 days, or a time range you configure.
  6. In the event list, handle events.

    • If you confirm that an event is a false alarm, locate the row containing the event. In the Operation column, click Handle as False Alarm and handle the hit rule.
      Figure 1 Handling a false alarm
      Table 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: Specify a domain name range this rule applies to.

      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.

      To add more domain names, click Add to add them one by one.

      www.example.com

      Condition List

      • Click Add in the condition box 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.
      • You can click Add outside the condition box to add a group of conditions. A maximum of three groups of conditions can be added. The relationship between multiple groups of conditions is or. So, the rule takes effect when one group of conditions is met.
      Parameters for configuring a condition are described as follows:
      • Field
      • Subfield: Configure this field only when IPv4, IPv6, Params, Cookie, or Header is selected for Field.
        NOTICE:

        A subfield cannot exceed 2,048 bytes.

      • 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.
      • Invalid requests: WAF can allow invalid requests.
        NOTE:

        A request is invalid if:

        • The request header contains more than 512 parameters.
        • The URL contains more than 2,048 parameters.
        • The request header contains "Content-Type:application/x-www-form-urlencoded", and the request body contains more than 8,192 parameters.

      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

      Rule ID

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

      Rule ID of a misreported event in Events whose type is not Custom. You are advised to handle false alarms on the Events page.

      041046

      Rule Type

      This parameter is mandatory when you select Attack type for Ignored 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.

      Ignore Field

      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 Field to configure a subfield.
      • If you select Body or Multipart, you can select All.
      • If you select Cookie, the Domain Name box for the rule can be empty.
      NOTE:

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

      Params

      All

    • Add the source IP address to an address group. Locate the row containing the desired event, in the Operation column, click More > Add to Address Group. The source IP address triggering the event will be blocked or allowed based on the policy used for the address group.

      Add to: You can select an existing address group or create an address group.

      Figure 2 Add to Address Group
    • Add the source IP address to a blacklist or whitelist rule of the corresponding protected domain name. Locate the row containing the desired event. In the Operation column, click More > Add to Blacklist/Whitelist. Then, the source IP address will be blocked or allowed based on the protective action configured in the blacklist or whitelist rule.
      Figure 3 Add to Blacklist/Whitelist
      Table 2 Parameter descriptions

      Parameter

      Description

      Add to

      • Existing rule
      • New rule

      Rule Name

      • If you select Existing rule for Add to, select a rule name from the drop-down list.
      • If you select New rule for Add to, customize a blacklist or whitelist rule.

      IP Address/Range/Group

      This parameter is mandatory when you select New rule for Add to.

      You can select IP address/Range or Address Group to add IP addresses a blacklist or whitelist rule.

      Group Name

      This parameter is mandatory when you select Address group for IP Address/Range/Group.

      Select an address group from the drop-down list. You can also click New address group to create an address group. For details, see Adding an IP Address Group.

      Protective Action

      • Block: Select Block if you want to blacklist an IP address or IP address range.
      • Allow: Select Allow if you want to whitelist an IP address or IP address range.
      • Log only: Select Log only if you want to observe an IP address or IP address range.

      Known Attack Source

      If you select Block for Protective Action, you can select a blocking type of a known attack source rule. WAF will block requests matching the configured IP address, Cookie, or Params for a length of time configured as part of the rule.

      Rule Description

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

Verification

A false alarm will be deleted within about a minute after the handling configuration is done. It will no longer be displayed in the attack event details list. You can refresh the browser cache and access the page for which the global whitelist rule is configured again to check whether the configuration is successful.

Related Operations

If an event is handled as a false alarm, the rule hit will be added to the global protection whitelist rule list. You can go to the Policies page and then switch to the Global Protection Whitelist page to manage the rule, including querying, disabling, deleting, and modifying the rule. For details, see Configuring a Global Protection Whitelist Rule.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback