Basic Principals of Use

To be able to use vWAF efficiently and to achieve a maximum increase in the security of your web applications, it’s vital to understand the underlying principles by which vWAF is structured and controlled.

This includes:

• logging in (see Starting Administration)
• information and control elements on the user interface (see Layout of the Administration Interface)
• the availability of features according to your user group (see Available Features )
• the different modes in which a ruleset can operate (see Detection Mode, Protection Mode)
• the availability of instant protection with minimum configuration effort (see Baseline Protection)
• the setup of applications and the mapping of requests to a particular application and thus to a particular ruleset (see Application Mapping, Paths, Preconditions)
• the option of inheriting properties and of setting up rules that are specific to a particular path (see Application Mapping, Paths, Preconditions)and Types of Handlers and Attribute Inheritance)
• the ability to distribute areas of responsibility across multiple persons (see Organizational Integration)
• the internal processing order (see How Blacklists, Whitelists, and Graylists Are Processed)
• saving and implementing changes (see When Changes Are Saved and Become Active).

•Starting Administration

•Layout of the Administration Interface

•Available Features

•Detection Mode, Protection Mode

•Baseline Protection

•Application Mapping, Paths, Preconditions

•How Blacklists, Whitelists, and Graylists Are Processed

•When Changes Are Saved and Become Active