Start monitoring your web applications

When a configuration change is detected in any of the web applications, the WAF appliance receives the configurations for all the deployed web applications. When the WAF server receives the configuration changes, it reloads the configuration at runtime to apply the changes.

The time that the WAF server takes to reload the configuration depends on the size of the configuration, which in turn depends on the number of web applications and the customized behavior settings configured on each web application.

To avoid the frequent updates that may cause latency, we recommend limiting the number of web applications deployed for each WAF appliance to 10.

If you keep the number of web applications deployed on each WAF appliance smaller, you will have a better WAF experience.

This is set to Blocking or Monitoring, depending on the web application settings in the Policies section.

When you add a web application we'll build a web asset in your subscription if it doesn't already exist. This asset has a name, URL and tags (optional) and it can be configured for other applications like WAS.

Where can I see my assets? You'll see an inventory of all the assets you have access to in AssetView (AV).. 

Users who are not Managers need to be granted access to web assets. A Manager can do this by going to the Administration utility, editing the users' accounts, and assigning web application tags to the users scopes.

Tagging web assets lets you grant users access to them. It also give you a convenient way to manage large volumes of web applications.