New features in Wallarm Cloud Dashboard

At Wallarm, we subscribe to the continuous delivery methodology. Some of you may have already seen these features as we have been releasing them over the past weeks.

For those of you who haven’t, this post will point out all the new shiny improvements for you.

Scanner tab

There is a new tab, Scanner, replacing the Scope tab in the main menu of Wallarm Console (my.wallarm.com). It combines

  • a map of customer network assets (domains, IP addresses, and ports) that have been automatically identified by Wallarm (data that previously appeared under Scope) and
  • controls and settings for Wallarm Scanner.

There are two main switches that control the Active Threat Verification module (rechecking attacks from live traffic) and Wallarm Scanner (running a variety of checks to discover new assets and to identify vulnerabilities and misconfiguration issues). Alternatively, you can turn scanning of each individual asset on and off by clicking on it in the asset map.

The left sidebar shows the current status of the scanner, including the number of assets that will be checked and an estimate of when the current phase of scanning will be finished.

Blacklists

The new update enables native support for request blocking by IP.

While most of the attacks are mitigated on a request-by-request basis, you need IP-based blacklists to mitigate behavioral-based attacks, such as credential stuffing or bruteforce.

For these types of attacks, individual requests are legitimate and do not contain malicious payloads (e.g., simple request to /api/login method with a login and password), but the behavior is abnormal and should be blocked by the IP address.

Previously, to block by blacklist, it was required to set up the integration of Wallarm blacklist with iptables or another firewall. In the new version, blocking by IP address happens right on the Wallarm Node (using underlying NGINX with a special module). Blacklists are configured in Settings -> Blacklists. You can turn on blacklists for specific locations that may be affected in your case (particular domain or some API methods as /api/login, etc.).

To take advantage of this feature, you need to make sure your nodes are updated to the latest release (release 2.8) and blocking by IP address is turned on in the node configuration file.

Custom rules

One of the major updates in the new version is the application profile view and custom rules.

By going to Settings -> Rules, you are now able to:

Set the traffic filtration mode for different locations;

You are still able to switch between blocking and non-blocking mode using local configuration files (and usually orchestration tools like Chef). It is now also possible to create a rule in the Wallarm Dashboard where all requests for a particular application or API (or requests that match other specified patterns) will be handled by blocking or non-blocking mode.

Create a regular expression to block a request by a static signature;

While the Wallarm attack detection engine doesn’t rely on signatures, some of our customers asked for the ability to extend our automated rules with custom rules they themselves create based on static regular expressions. This was mostly needed for convenience while migrating from signature-based solutions (such as mod_security) to keep using existing rule sets.

Create a virtual patch if you want to block some particular requests while Wallarm Node operates in monitoring mode;

This new feature is pretty much as you would expect. You can configure the ability to create a virtual patch for any of the standard vulnerabilities such as SQLi or RCE to prevent their exploitation for some application endpoints, even if Wallarm is configured to operate in monitoring mode.

Apply data masking within malicious requests to eliminate the chance of exposing sensitive data in the Wallarm Cloud Dashboard.

The only case where some actual data from the traffic can be transferred to the Wallarm Dashboard is as a part of a malicious request. To eliminate the possibility of any confidential data being exposed in the Wallarm Dashboard, you can mask sensitive fields (such as cookies, names, passwords, session, etc.) by creating corresponding rules. This will make these data redacted before sending them out to the cloud for further analysis.

Find more information in the docs. There is a dedicated post coming about the new Rules section soon.