Trigger examples¶

Learn real examples of Wallarm triggers to better understand this feature and configure triggers appropriately.

Graylist IP if 4 or more malicious payloads are detected in 1 hour¶

If 4 or more different malicious payloads are sent to the protected resource from one IP address, this IP address will be graylisted for 1 hour.

If you have recently created the Wallarm account, this trigger is already created and enabled. You can edit, disable, delete, or copy this trigger as well as the manually created triggers.

To test the trigger:

Send the following requests to the protected resource:

curl 'http://localhost/?id=1%27%20UNION%20SELECT%20username,%20password%20FROM%20users--<script>prompt(1)</script>'
curl 'http://localhost/?id=1%27%20select%20version();'
curl http://localhost/instructions.php/etc/passwd

There are 4 malicious payloads of the SQLi, XSS, and Path Traversal types.

Open Wallarm Console → IP lists → Graylist and check that the IP address from which the requests originated is graylisted for 1 hour.
Open the section Events and check that the attacks are displayed in the list:

To search for attacks, you can use the filters, for example: sqli for the SQLi attacks, xss for the XSS attacks, ptrav for the Path Traversal attacks. All filters are described in the instructions on search use.

The trigger is released in any node filtration mode, so that it will graylist IPs regardless of the node mode. However, the node analyzes the graylist only in the safe blocking mode. To block malicious requests originating from graylisted IPs, switch the node mode to safe blocking learning its features first.

Denylist IP if 4 or more malicious payloads are detected in 1 hour¶

If 4 or more different malicious payloads are sent to the protected resource from one IP address, this IP address will be denylisted for 1 hour.

To test the trigger:

Send the following requests to the protected resource:

curl 'http://localhost/?id=1%27%20UNION%20SELECT%20username,%20password%20FROM%20users--<script>prompt(1)</script>'
curl 'http://localhost/?id=1%27%20select%20version();'
curl http://localhost/instructions.php/etc/passwd

There are 4 malicious payloads of the SQLi, XSS, and Path Traversal types.

Open Wallarm Console → IP lists → Denylist and check that the IP address from which the requests originated is blocked for 1 hour.
Open the section Events and check that the attacks are displayed in the list:

To search for attacks, you can use the filters, for example: sqli for the SQLi attacks, xss for the XSS attacks, ptrav for the Path Traversal attacks. All filters are described in the instructions on search use.

If an IP address was denylisted by this trigger, the filtering node would block all malicious and legitimate requests that originated from this IP. To allow legitimate requests, you can configure the graylisting trigger.

Mark requests as a brute‑force attack if 31 or more requests are sent to the protected resource¶

To mark requests as a regular brute-force attack, the trigger with the condition Brute force should be configured.

If 31 or more requests are sent to https://example.com/api/v1/login in 30 seconds, these requests will be marked as brute‑force attack and the IP address from which the requests originated will be added to the denylist.

Details on configuration of brute force protection and trigger testing →

Mark requests as a forced browsing attack if the 404 code is returned to 31 or more requests¶

To mark requests as a forced browsing attack, the trigger with the condition Forced browsing should be configured.

If the endpoint https://example.com/**.** returns 404 response code 31 or more times in 30 seconds, appropriate requests will be marked as a forced browsing attack and a source IP address of these requests will be blocked.

Endpoint examples matching the URI value are https://example.com/config.json, https://example.com/password.txt.

Details on configuration of brute force protection and trigger testing →

Mark requests as the BOLA attack¶

If 31 or more requests are sent to https://example.com/shops/{shop_id}/financial_info in 30 seconds, these requests will be marked as the BOLA attack and the IP address from which the requests originated will be added to the denylist.

Details on configuration of BOLA protection and trigger testing →

Detect weak JWTs¶

If a significant amount of incoming requests processed by the node 4.4 contains weak JWTs, record the corresponding vulnerability.

Weak JWTs are those that are:

Unencrypted - there is no signing algorithm (the alg field is none or absent).
Signed using compromised secret keys

If you have recently created the Wallarm account, this trigger is already created and enabled. You can edit, disable, delete, or copy this trigger as well as the manually created triggers.

To test the trigger:

Generate a JWT signed using a compromised secret key, e.g.:

eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyLCJyb2xlIjoiQWRtaW5pc3RyYXRvciJ9.p5DrumkF6oTBiUmdtDRT5YHqYL2D7p5YOp6quUrULYg

Generate some traffic with requests authenticated using a compromised JWT.
If a significant amount of incoming requests processed by the node 4.4 contains weak JWTs, Wallarm registers the vulnerability, e.g.:

Slack notification if 2 or more SQLi hits are detected in one minute¶

If 2 or more SQLi hits are sent to the protected resource, then a notification about this event will be sent to the Slack channel.

Example of a trigger sending the notification to Slack

To test the trigger:

Send the following requests to the protected resource:

curl 'http://localhost/?id=1%27%20UNION%20SELECT%20username,%20password%20FROM%20users--<script>prompt(1)</script>'
curl 'http://localhost/?id=1%27%20select%20version();'

Open the Slack channel and check that the following notification from the user wallarm received:

[Wallarm] Trigger: The number of detected hits exceeded the threshold

Notification type: attacks_exceeded

The number of detected hits exceeded 1 in 1 minute.
This notification was triggered by the "Notification about SQLi hits" trigger.

Additional trigger’s clauses:
Attack type: SQLi.

View events:
https://my.wallarm.com/search?q=attacks&time_from=XXXXXXXXXX&time_to=XXXXXXXXXX

Client: TestCompany
Cloud: EU

Notification about SQLi hits is the trigger name
TestCompany is the name of your company account in Wallarm Console
EU is the Wallarm Cloud where your company account is registered

Slack and email notification if new user is added to the account¶

If a new user with the Administrator or Analyst role is added to the company account in Wallarm Console, notification about this event will be sent to the email address specified in the integration and to the Slack channel.

Example of a trigger sending the notification to Slack and by email

To test the trigger:

Open the Wallarm Console → Settings → Users and add a new user. For example:
Open your email Inbox and check that the following message received:
Open the Slack channel and check that the following notification from the user wallarm received:
```
[Wallarm] Trigger: New user was added to the company account

Notification type: create_user

A new user John Smith <johnsmith@example.com> with the role Analyst was added to the company account by John Doe <johndoe@example.com>.
This notification was triggered by the "Added user" trigger.

Client: TestCompany
Cloud: EU
```
- John Smith and johnsmith@example.com is information about the added user
- Analyst is the role of the added user
- John Doe and johndoe@example.com is information about the user who added a new user
- Added user is the trigger name
- TestCompany is the name of your company account in Wallarm Console
- EU is the Wallarm Cloud where your company account is registered

Opsgenie notification if 2 or more incidents are detected in one second¶

If 2 or more incidents with the application server or database are detected in one second, the notification about this event will be sent to Opsgenie.

Example of a trigger sending the data to Splunk

To test the trigger, it is required to send the attack exploiting an active vulnerability to the protected resource. The Wallarm Console → Vulnerabilities section displays active vulnerabilities detected in your applications and the examples of attacks that exploit these vulnerabilities.

If the attack example is sent to the protected resource, Wallarm will record the incident. Two or more recorded incidents will trigger sending the following notification to Opsgenie:

[Wallarm] Trigger: The number of incidents exceeded the threshold

Notification type: incidents_exceeded

The number of detected incidents exceeded 1 in 1 second.
This notification was triggered by the "Notification about incidents" trigger.

Additional trigger’s clauses:
Target: server, database.

View events:
https://my.wallarm.com/search?q=incidents&time_from=XXXXXXXXXX&time_to=XXXXXXXXXX

Client: TestCompany
Cloud: EU

Notification about incidents is the trigger name
TestCompany is the name of your company account in Wallarm Console
EU is the Wallarm Cloud where your company account is registered

Protecting the resource from active vulnerability exploitation

To protect the resource from active vulnerability exploitation, we recommend patching the vulnerability in a timely manner. If the vulnerability cannot be patched on the application side, please configure a virtual patch to block attacks exploiting this vulnerability.

Notification to Webhook URL if IP address is added to the denylist¶

If an IP address was added to the denylist, the webhook about this event will be sent to Webhook URL.

To test the trigger:

Open the Wallarm Console → IP lists → Denylist and add the IP address to the denylist. For example:

Check that the following webhook was sent to the Webhook URL:

[
    {
        "summary": "[Wallarm] Trigger: New IP address was denylisted",
        "description": "Notification type: ip_blocked\n\nIP address 1.1.1.1 was denylisted until 2021-06-10 02:27:15 +0300 for the reason Produces many attacks. You can review blocked IP addresses in the \"Denylist\" section of Wallarm Console.\nThis notification was triggered by the \"Notification about denylisted IP\" trigger. The IP is blocked for the application Application #8.\n\nClient: TestCompany\nCloud: EU\n",
        "details": {
        "client_name": "TestCompany",
        "cloud": "EU",
        "notification_type": "ip_blocked",
        "trigger_name": "Notification about denylisted IP",
        "application": "Application #8",
        "reason": "Produces many attacks",
        "expire_at": "2021-06-10 02:27:15 +0300",
        "ip": "1.1.1.1"
        }
    }
]

Notification about denylisted IP is the trigger name
TestCompany is the name of your company account in Wallarm Console
EU is the Wallarm Cloud where your company account is registered

Group hits originating from the same IP into one attack¶

If more than 50 hits from the same IP address are detected in 15 minutes, the next hits from the same IP will be grouped into one attack in the event list.

If you have recently created the Wallarm account, this trigger is already created and enabled. You can edit, disable, delete, or copy this trigger as well as the manually created triggers.

To test the trigger, send 51 or more hits as follows:

All hits are sent in 15 minutes
The IP addresses of the hit sources are the same
Hits have different attack types or parameters with malicious payloads or addresses the hits are sent to (so that the hits are not grouped into an attack by the basic method)
Attack types are different from Brute force, Forced browsing, Resource overlimit, Data bomb and Virtual patch

Example:

10 hits to example.com
20 hits to test.com
40 hits to example-domain.com

The first 50 hits will appear in the event list as individual hits. All of the following hits will be grouped into one attack, e.g.:

The Mark as false positive button and the active verification option will be unavailable for the attack.

New endpoints in your API inventory¶

Changes may occur in your API. They will be discovered by the API Discovery module. Possible changes are:

A new endpoint is discovered
An endpoint has changes (new or deleted parameters)
An endpoint is removed

To get notifications about some or all of these changes to your email or messenger, the trigger with the Changes in API condition should be configured.

In this example, if new endpoints for the example.com API host are discovered by the API Discovery module, the notification about this will be sent to your configured Slack channel.

To test the trigger:

In Integrations, configure integration with Slack.
In Triggers, create trigger as shown above.
Send several requests to the example.com/users endpoint to get the 200 (OK) response.
In the API Discovery section, check that your endpoint was added with the New mark.

Check messages in your Slack channel like:

[wallarm] A new endpoint has been discovered in your API

Notification type: api_structure_changed

The new GET example.com/users endpoint has been discovered in your API.

    Client: Client 001
    Cloud: US

    Details:

      application: Application 1802
      domain: example.com
      endpoint_path: /users
      http_method: GET
      change_type: added
      link: https://my.wallarm.com/api-discovery?instance=1802&method=GET&q=example.com%2Fusers