See the Wallarm documentation for more details.We have improved our dashboards to make it easier to analyze malicious traffic and identify critical attack vectors:

• The new API Protocols widget raises the visibility of the system's protocols and the associated attacks. This widget helps you to detect the emergence of new unapproved protocols or track a significant change in the number of attacks. With one click you can go from the widget to the Events tab to analyze the details of attacks on the selected protocol.

• The Attack Sources and Attack Targets widgets are now more compact, making it easier to analyze the location of threat sources and the assets that these threats are directed at. The widget "Attack Targets" have now two view option: statistics by domains and statistics by applications. This enables you to analyze attacks surface even for misconfigured applications.

See the Wallarm documentation for more details.

It's now easier to configure protection against API abuse, bruteforce or dirbusting attacks. Use an updated interface of Triggers:

• The Bruteforce trigger defines classic bruteforce attack protection against specific URI based on the number of incoming requests.
• The Forced browsing trigger forced browsing attacks allows to protect your apps against dirbusting (based on application 404 response codes)

In the simplest case, it is enough to enter the URI when creating the trigger. Wallarm will collect statistics from all the distributed Wallarm nodes deployed across your whole infrastructure.

When required, you can also use regular expressions (for example. wildcard URLs) or specify specific request headers (such as cookies) using the advanced view. Read more in our documentation.

Note: There is no need to edit your existing rules. However, previous rules “Add forced browsing attack tag to requests”, “Add brute force attacks tag to requests” will no longer be visible in the Rules section.