System Configuration

Determines the user group to which new users are assigned when AdminAuthAutoAddUsers is true.

When this option is set to true, users of the Traffic Manager who access vWAF for the first time are automatically added as vWAF users. In this case you don't need to add these users manually via User Management

By default, the added users are assigned to the user group "zeusafm Administrator". You can change this by setting the attribute AdminAuthAutoAddUserGroup.

URL to which users are redirected after manual or automatic logout.

Usually, vWAF uses external authentication via the Traffic Manager. If you change the default setting to "internal", vWAF uses a separate authentication mechanism and login page. Users then have to log in using the username and password specified in User Management.

Default IP address of the Admin Master Server.

Default port number of the Admin Master Server.

With large installations, the administration master can be a performance bottleneck for user interface operations. Tasks like fetching statistical data or doing statistic precomputations can take up a lot of CPU resources. This can make the user interface act slow, or it might even delay other important tasks. To increase performance, you can enable multi-CPU mode. The downside of multi-CPU mode, however, is that it needs more memory. So the decision is a tradeoff between performance and memory usage.

IP address of the administration server.

Port number of the administration server.

Timeout of the administration server, given in minutes. The value must be in the interval of 5 up to 720 minutes (= 12 hours).

SSL cert file if SSL is used to access the administration interface. If no key and cert files are specified, vWAF uses default values.)

SSL key file if SSL is used to access the administration interface. (If no key and cert files are specified, vWAF uses default values.)

When enabled, SSL is used to access the vWAF administration interface.

Default IP address of the Admin Slave Server.

If vWAF isn't installed in a cluster, the Admin Master Server and Admin Slave Server run on the same computer.

Default port number of the Admin Slave Server.

Cluster password.

IP address of the decider.

Port number of the decider.

This entry must match the port configured in the web server (entry AODbackend.

Directory where the online documentation is stored. The default is doc.

Determines whether vWAF automatically downloads definition files for baseline protection (see Baseline Protection).

You can set this option to true temporarily if you've forgotten your username or password. You can then use the default username "admin" and password "admin" to log in and then change your password.

For security reasons, comment the option back out again as soon as possible, or set the value to "false".

IP address of the decider that's used as hot standby node.

Port number of the decider that's used as hot standby node.

Only when installed in an cluster:

Determines whether a slave node is configured for hot standby mode. In hot standby mode this decider is used if other deciders aren't available.

Specifies where the system log files are stored.

To specify where the application specific log files, are stored, use the attributes "slaveLogBackend" and "masterLogBackend". Usually, we recommend using the same directory for "logDir" as for "slaveLogBackend".

see slaveLogBackend

Maximum number of IP addresses for which temporary blacklisting may be activated (see Global IP Blacklisting ).

Unique ID for each slave.

Number of CPUs if multi-CPU support has been enabled (see Installation).

Determines whether log files are automatically removed from slaves after successful synchronization (default is False).

Only needed if you use the REST-based API.

IP address of the used REST server.

Only needed if you use the REST-based API.

Port number of the used REST server.

SSL cert file if SSL is used to access the REST server. If no key and cert files are specified, vWAF uses default values.)

SSL key file if SSL is used to access the REST server. (If no key and cert files are specified, vWAF uses default values.)

Only needed if you use the REST-based API.

True if the used REST server uses SSL.

Back-ends for the log files:

For masterLogBackend to become effective, the option useMasterLogs must be enabled.

At least one back-end is required. You can also specify multiple log back-ends at a time, separated by commas.

When you specify multiple back-ends, vWAF uses the first back-end (the entry before the first comma) when it reads and displays log data for monitoring.

Possible back-ends and the required definition syntax are:

The variable elements must not contain commas or any of the special characters used to define a log backend.

A typical scenario is logging to a file on the slaves, and to a database on the master.

Example:

slaveLogBackend = file:../generic/logs, syslog:10.100.1.1 masterLogBackend = db:postgres://stingrayaf@localhost//stingrayaf_master_log

If you want to use a database as a log back-end, make sure that you have the appropriate know-how of how to configure and tune the performance of that database. We can't provide any support, here. If you aren't sure of how to configure a database, we strongly recommend using a file log back-end instead.

IP address of the SNMP agent.

Port number of the SNMP agent.

Directory where the configuration databases and statistics are stored. The default is "conf".

vWAF saves log files on all slaves. If you want to be able to back up and analyze log files centrally, vWAF can additionally save copies of the log files on the master. To achieve this, you must set useMasterLogs to True on the master.

Saving copies on the master may take up a lot of disk space. Therefore this feature is disabled by default (Value False).