Skip to content

Migrating whitelists and blacklists from previous Wallarm node versions to 3.0

Starting with Wallarm node 3.0, the method of IP addresses whitelist and blacklist configuration has been changed. This document instructs how to migrate whitelists ad blacklists configured in Wallarm node 2.18 or lower to Wallarm node 3.0.

What has changed?

Configuration of IP addresses whitelist and blacklist has been changed as follows:

  • The wallarm_acl_* NGINX directives, acl Envoy parameters, and WALLARM_ACL_* environment variables have been deprecated. Now, IP lists are configured as follows:

    • Additional steps to enable IP whitelisting or blacklisting functionality are not required. The Wallarm node downloads IP addresses lists from the Wallarm Cloud by default and applies downloaded data when processing incoming requests.
    • Blocking page and error code returned in the response to the blocked request are configured using the wallarm_block_page directive instead of wallarm_acl_block_page.

  • Whitelisted and blacklisted IP addresses are managed via the Wallarm Console.

  • IP addresses of Wallarm Vulnerability Scanner are whitelisted by default. Manual whitelisting of Scanner IP addresses is no longer required.

Procedure for whitelists and blacklists configuration migration

  1. Inform Wallarm technical support that you are updating filtering node modules up to 3.0 and ask to enable new IP lists logic for your Wallarm account. When new IP lists logic is enabled, please open the Wallarm Console and ensure that the section IP lists is available.

  2. Update the filtering node modules up to version 3.0 following appropriate instructions.

  3. Remove the whitelist of Wallarm Scanner IP addresses from filtering node configuration files. Starting with the filtering node 3.0, Scanner IP addresses are whitelisted by default. In previous Wallarm node versions, the whitelist could be configured by the following methods:

  4. If listed methods are used to whitelist other IP addresses that should not be blocked by the filtering node, please move them to the whitelist in the Wallarm Console.

  5. If you have used the directive wallarm_acl_block_page to configure the blocking page and error code returned when the blacklisted IP originated the request, please replace the directive name by wallarm_block_page and update its value following the instructions.

  6. Remove the NGINX and Envoy environment variables WALLARM_ACL_* from the docker run commands.

  7. (Optional) Remove the NGINX directives wallarm_acl_* and acl Envoy parameters from filtering node configuration files.