Learn more | Nemesida WAF

Guide to solving main issues while setting up and operating the Nemesida WAF.

Due to the termination of support for docker containers nwaf-web/nwaf-web-pg, it is necessary to migrate components to new containers Nemesida WAF API and Nemesida WAF Cabinet.

The Nemesida WAF is a complex consisting of several components interacting with each other. Incorrect configuration of one of the components can lead to its malfunction or the malfunction of the entire complex. Below is a list of the main actions that must be performed to verify the correct configuration of each component of the

Though we are constantly working on optimizing all Nemesida WAF components, there is a possibility of an emergency situation. Similar situations include:

To use a web server with filtering node as an intermediate server, you should create corresponding file of the virtual host (for example /etc/nginx/conf.d/example.com.conf).

The Nemesida WAF API module is the key link between all Nemesida WAF components, so it is necessary to ensure its fault-tolerant operation. In this article we will explain how to do it.

Nemesida WAF allows to automatically deal with brute force, flood and DDoS attacks. Setup Nemesida WAF Cabinet allows you to configure Nemesida WAF parameters to protect the web application using the web interface. To activate the functionality, you need to perform the following actions: 1. Make the minimal settings on servers with Nemesida WAF modules

Nemesida WAF can be integrated with external SIEM systems. To do this, you need to configure the collection of events from all servers where Nemesida WAF is installed. There are several ways to do this.