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 Application Firewall

Creating an HTTPS Service

  • Last updated on

You must configure a certificate before you can configure an HTTPS service. For more information, see Configuring SSL for Services and Servers.

An HTTPS service is a controlled entry point for an encrypted HTTPS web application on the server. This service handles encrypted transactions between clients and the Barracuda Web Application Firewall, authenticating itself using a configured certificate, also while acting as a server to requesting clients. To create an HTTPS service, select HTTPS as the type of service. For additional instructions, go to the BASIC > Services page and click Help.

With HTTPS, HTTP uses SSL/TLS to initiate a secure connection to the application. The SSL/TLS protocols provide an encrypted connection using a set of cipher suites to encrypt the traffic. SSLv3 is the oldest of these protocols, succeeded by TLS1.0, TLS1.1, and TLS1.2. Each of these protocols supports a specific set of cipher suites. Over the last few years, many vulnerabilities have been discovered in the SSL/TLS protocols and the cipher suites that they use. Due to these vulnerabilities, the current recommendation is to disable SSLv3 and use only the TLS protocols. The preferred TLS protocol is TLS1.2, however, TLS1.1 offers the best mix of security and compatibility. Cipher suites also have vulnerabilities; some of these vulnerabilities target a specific protocol/cipher suite combination. For example, the BEAST targets SSL v3.0 and TLS 1.0 when used with block ciphers.

To help migrate smoothly to more secure protocols and cipher suites, the Barracuda Web Application Firewall now allows administrators to select specific cipher suites for each protocol. Instead of using the same set of cipher suites for all protocols, you can now configure an override list for each of the protocols. Once configured, each protocol will only use its own override list to negotiate the configuration.

To configure the cipher override list:

  1. Go to the BASIC > Services page.
  2. Click Edit next to an HTTPS service. The Edit Service Configuration window appears.
  3. Scroll down to the SSL section, and click Show Advanced Settings.
  4. Under Override Ciphers:
    1. For each protocol version, select the ciphers you want to include from the Available Ciphers list, and then click Add.
    2. Click Save.

For more information on secure protocol and cipher suite combinations, you can refer to the NIST article or Mozilla wiki:

Last updated on