It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Web Application Firewall

You are currently viewing the legacy Barracuda Campus portal

Due to ongoing compatibility requirements during the migration, some users are still being redirected here. All content is being transitioned to the new Campus Training Portal and Campus Documentation Portal, and this legacy portal will be fully retired once the migration is complete.

Please visit https://campus.barracuda.com for more information.

Deployment

  • Last updated on

Deployment Modes

The Barracuda Web Application Firewall can be deployed as a reverse proxy, in Two-Arm Proxy or in One-Arm Proxy configuration. Alternatively, it can be deployed in a bridge-path configuration with the Barracuda Web Application Firewall appliance - but bridge-path is not supported by the Barracuda Web Application Firewall Vx virtual machine.

For more information, see Choosing Your Deployment Mode.

Best Practices

The goal of this article is to provide administrators with common best practice considerations as they are configuring their Barracuda Web Application Firewall to ensure the highest level of security and availability. This article should be used in conjunction with the other Barracuda Web Application Firewall articles and the Barracuda Web Application Firewall Online help, which provides in-depth information on how to configure the Barracuda Web Application Firewall.

For more information, see Deployment Best Practices.

Virtual Deployment

The Barracuda Web Application Firewall Vx protects web applications from data breaches.

For more information, see Virtual Deployment.

Public Cloud Hosting

Barracuda Networks offers the Barracuda Web Application Firewall Vx as a cloud-hosted virtual machine, protecting your applications that are set up in the public cloud or in private networks.

For more information, see Public Cloud Hosting.