Skip to content

Analyzing Attacks

You can check attacks in the Events tab of the Wallarm interface.

Wallarm automatically groups associated malicious requests into one entity — an attack.

Analyze an Attack

You can get information about an attack by investigating all the table columns described in “Checking Attacks and Incidents.”

Analyze Requests in an Attack

  1. Select an attack.

  2. Click the number in the Requests column.

Clicking the number will unfold all requests in the selected attack.

Requests in the attack

Each request displays the associated information in the following columns:

  • Date: Date and time of the request.

  • Payload: malicious payload. Clicking the value in the payload column displays reference information on the attack type.

  • Source: The IP address from which the request originated. Clicking the IP address adds the IP address value into the search field. The following information is also displayed if it was found in the Wallarm databases:

    • The country in which the IP address is registered
    • Which data center the given IP addresses belong to: the AWS tag for Amazon, the GCP tag for Google, the Azure tag for Microsoft data centers, and DC for other data centers
    • The Tor tag if the attack's source is the Tor network
    • The VPN tag if IP address belongs to VPN
    • The Public proxy or Web proxy tag if the request was sent from the public or web proxy server
  • Status: The server's response status code from the request.

  • Size: The server's response size.

  • Time: The server's response time.

If the attack is happening at the current moment, the “now” label is shown under the request graph.

A currently happening attack

Analyze a Request in Raw Format

The raw format of a request is the maximum possible level of detail.

  1. Select an attack.

  2. Click the number in the Requests column.

  3. Click the arrow next to the date of the request.

The Wallarm interface will display the request in its raw format.

Raw format of the request

Sampling of hits

The attack may consist of a large number of identical hits (more than 100). Storing all hits may increase the Wallarm Cloud load and require a considerable amount of time to analyze and search for attacks via the Wallarm Console.

To optimize the data storage and analysis, we apply the sampling algorithm to hits:

  • The first 5 identical hits for each hour are saved in the sample in the Wallarm Cloud. If several samples are the part of the same attack, these samples are grouped (for example, the hits in the samples may differ only in the IP addresses).

  • The rest of the hits are not saved in the sample, but their number is recorded in a separate parameter for each attack.


  • If the attack consists of 20 hits (10 identical hits each originated from different IP addresses), data on the first 5 hits from each IP address will be saved in the sample in the Wallarm Cloud and the number of the rest hits (10) will be recorded in a separate variable.

  • If the attack consists of 10 hits originated from different IP addresses, data on all hits will be saved in the Wallarm Cloud.

Enabling the sampling algorithm

  • For input validation attacks, the sampling algorithm is enabled if Wallarm detects a high percentage of attacks in your traffic.

    When the sampling algorithm is enabled, all users of the Administrator or Global Administrator role added to your company account will receive a corresponding email. Emails are sent once per 8 hours if the sampling algorithm is enabled / disabled due to the attack percentage change.

  • For all behavioral attacks, the sampling algorithm is enabled by default.

If hits sampling is enabled for your traffic, the appropriate status, the sample of saved hits, and the number of other hits are displayed in the Events section of the Wallarm Console. For example:

Dropped hits

Demo videos