Skip to content

What is new in Wallarm node 5.0

We are excited to announce the release of Wallarm Node 5.0! This major release introduces changes to our technology stack.

Overview

The Wallarm node has been re-engineered, transitioning from a Ruby-based implementation to one based on the Go language. With this release, we focus on making the solution faster, more scalable, and more resource-efficient, both now and for the future development.

Regarding the exact metrics, the following performance improvements have been made in the Wallarm postanalytics module:

  • CPU consumption has been decreased from 0.5 CPU cores to 0.1 CPU cores.

  • Memory consumption has been reduced by 400 MB at a traffic rate of 500 requests per second.

This release focuses on technical refactoring and does not introduce any changes in Wallarm functionality. All the features supported by the previous node version 4.10 are also present in 5.0.

File system changes

The following changes have been introduced in the file system of the Wallarm deployment artifacts:

  • Log file system: Previously, logs were recorded in multiple files, each for a dedicated script. Now, logs from almost all services are recorded into a single dedicated file, wcli-out.log. You can review the list of previous log files and the current one.

  • The diagnostic script path change: The /opt/wallarm/usr/share/wallarm-common/collect-info.sh file has been moved to /opt/wallarm/collect-info.sh.

Customizing sensitive data detection in API Discovery (node 5.0.3 and higher)

API Discovery detects and highlights sensitive data consumed and carried by your APIs. Starting from version 5.0.3, you can fine-tune the existing detection process and add your own sensitive data patterns.

Patterns are used to define which sensitive data is detected and how. To modify default patterns and add your own, in Wallarm Console go to API Discovery → Configure API Discovery → Sensitive data.

Further feature introduction

Starting with release 5.2, new features will be introduced exclusively in the node with the new Go-based implementation. Per our versioning policy, these new features will not be backported to the previous version (4.10).

New deployment option for TCP traffic mirror analysis

With the launch of release 5.0, Wallarm introduces an artifact specifically designed for TCP traffic mirror analysis. This new deployment option, based on our advanced re-engineered node, enhances your ability to monitor and secure TCP traffic directly at the network layer.

Deployment instructions

  • Client and multi-tenant Wallarm nodes of version 4.8 and 4.10 to stay up to date with Wallarm releases and prevent installed module deprecation.

  • Client and multi-tenant Wallarm nodes of the unsupported versions (4.6 and lower).

    If upgrading from the version 3.6 or lower, learn all changes from the separate list.

Upgrade process

  1. Review recommendations for the module upgrade.

  2. Upgrade installed modules following the instructions for your Wallarm node deployment option:

Other updates in Wallarm products and components →