We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Web Security Gateway

Deploying the Barracuda Web Security Gateway with a Peer Proxy

  • Last updated on

In this deployment, the Barracuda Web Security Gateway is deployed inline or as a proxy and is configured to forward all port 80 traffic to a pre-existing proxy server. The proxy server can be anywhere on or off the network, and it sends filtered traffic from the Barracuda Web Security Gateway to the Internet. The Barracuda Web Security Gateway just needs to be configured with the IP address and port of the proxy server as described below. Note that HTTPS(443) traffic will go straight out to the internet after being filtered, even with SSL Inspection configured.

For this deployment, configure the following on the ADVANCED > Proxy page of the Barracuda Web Security Gateway web interface:

  1. Peer Proxy IP: Enter the IP address of a pre-existing proxy server which will forward traffic from the Barracuda Web Security Gateway to the Internet. 
  2. Peer Proxy Port: If you have a pre-existing proxy server, enter the port number used for HTTP requests. 

Using SSL Inspection

If you have this feature enabled on the Barracuda Web Security Gateway, to protect sensitive data, it is recommended to only use SSL Inspection if the peer proxy server is deployed inside the firewall. To use SSL Inspection, see How To Configure SSL Inspection.How to Configure SSL Inspection Version 7.1

Using Authentication

Authentication is supported with a peer proxy if the Barracuda Web Security Gateway is deployed in a proxy configuration. See Forward Proxy Deployment of the Barracuda Web Security Gateway.

Last updated on