Go to Web Applications and click New Web Application above the list. For each web app you want to protect enter asset details, application settings, security information, and assign a firewall cluster. Create security policies, application profiles, and custom rules, which you can then assign to your web application. For security policy, you can use the Pass-through policy or a policy template, or you can create a custom one.
Tip - Turn help tips on in the wizard title bar to get help - just hover over the field names and we'll help you along the way.
You'll assign a security policy to each of your web applications. We'll use this to monitor the web applications and report security events. A web app's security policy determines responses to certain types of incoming traffic and the handling of outgoing traffic - this impacts what security events we'll report for the web application and whether or not we'll actively block malicious traffic. Use a ready made system policy or a policy template, or simply start with a blank policy.
Want to create a policy? It's easy - just to go Security > Policies and select New Policy. Learn more
You can create reusable profiles for settings which can be commonly used by multiple Web applications. Reusable profiles can be created for Web server pools, healthcheck parameters, SSL certificates, custom response pages, and HTTP filters. You can also create these profiles directly from within the web application wizard. Learn more
Web Server Pool Profile: Creating a server pool helps you load balance traffic between multiple servers.
Healthcheck Profile: Creating heathchecks helps you verify the availability of the your web application servers.
SSL Certificate Profile: You can enable SSL for site URLs and provide a PKCS12 file, or simply copy-paste the contents of the certificate, private key, and passphrase directly into the UI
Custom Response Pages: Instead of the default WAF error page, you can choose to display a custom page if your security policy blocks a particular section or a page on your web site or if a request cannot be routed to your origin server.
You can filter protocol oriented attributes and configure options for anomalies, information leakage, cookies, clickjacking, browser XSS protection, and so on.. Learn more
You can create conditions and actions using custom rules to block access or provide exceptions for accessing certain resources in the Web application. Learn more
Tags give you a way to organize your web applications and to permit users to access them. When you apply a tag to a web application, all users whose scopes include that tag will have access to it. Learn more
You can quickly see the status for a web application on the web applications list. Tip - Hover over the icon to see what it means.
Pending means the web app configuration is being updated and deployed.
Active means that the web app is deployed in only active WAF clusters.
Degraded means that one or more of the clusters the web app is deployed in are not active.
Inactive means that the web app either is not deployed or is deployed in only inactive clusters.
You can remove web applications one at a time or in bulk. Keep in mind if you remove a web application that already has security events data, we'll delete all the events data for the web application from your account, and this can't be retrieved later.
How do I do it? Just select the web application(s) you want to delete and select Remove Web Assets from the Actions menu. Or use the Quick Actions menu if you want to delete just one.
Tell me about permissions. You must be a Manager, a user assigned full rights, or a user with the permission Delete WAF Asset. A Manager can assign users this permission using the Administration utility.
You can quickly deploy web applications and configurations to a cluster by using the Quick Actions menu. Simply go to the Web Applications tab, and from the Quick Actions menu of a web application, click Force Deployment. Click confirm at the message asking you to confirm the force deployment.
The web application and its configurations are deployed to associated WAF clusters and registered appliances. The deployment status gets updated once the Web application and configurations are deployed.
You can associate a cluster to a web application either through the Web Applications wizard, or through the Quick Actions menu of a web application.