Barracuda Web Application Firewall Release Notes - Version (Pre requisite :

Before installing a new version of firmware:
  1. Make a backup of your configuration using the ADVANCED > Backup page.
  2. Read all release notes that apply to versions more recent than the one currently running on your system.
The update process typically takes only a few minutes after the update is applied. Make sure you do not reboot the machine during this time. The progress bar would indicate the status but in some rare cases, the progress bar may not be seen. If this happens, please revisit the URL after five minutes. If the process takes longer, contact Barracuda Networks Technical Support to investigate.


  • The upgrade when coming from 9.0.x to 9.1.0, will be a major one and the upgrade process, may take more than 10 minutes in case the configuration is large, specially with many servers configured. Please donot reboot the machine while the upgrade process is in progress
  • Downgrading to a previous major version (like from 9.1.x to 9.0.x) is NOT recommended. Please contact Barracuda Networks Technical Support if you are thinking about attempting a firmware downgrade, and make sure that you have carefully gone through the known issues sections for the earlier firmware versions.

Backups taken AFTER a firmware revert or downgrade (such as from 9.1.x to 9.0.x), may not be compatible for use after a subsequent firmware upgrade (such as from 9.0.x back up to 9.1.x), so make sure that you back up your configuration settings BEFORE actually start any firmware change process (either upgrade OR revert). If a feature is available in later versions and the configuration is in place for that feature, a downgrade does retain the configuration. This means that after the downgrade, the configuration pertaining to such a feature might be visible but would not take effect.

After restoring your settings from a backup, you should always REBOOT to make sure that they take effect.

NOTE: On an upgrade to 7.9.x, older web firewall logs and access logs will no longer be available on the User Interface. It is advised to export relevant logs using one or more of the available options under Advanced > Export Logs, before commencing the upgrade.

Barracuda Web Application Firewall Product Activation

If this is a new system, you must activate your Energize Updates subscription prior to initial use. Your Energize Updates subscription includes access to Technical Support, new firmware releases and ongoing security definitions updates.
To activate your Barracuda Web Application Firewall subscription:
  1. Using your Web browser, go to the BASIC > Status page.
  2. In the Subscription Status section, check the Energize Updates entry. If Energize Updates is Not Activated, click the activation link to be redirected to the Barracuda Networks Product Activation page. Complete activation of your subscription(s).
If it is connected to the Internet, your Barracuda Web Application Firewall automatically updates its activation status after you reload the browser page when viewing the BASIC > Status page. If it is not connected to the Internet yet, enter the activation code provided after completing the details on the Barracuda Networks Product Activation page. Click Activate. If the code is correct, the Barracuda Web Application Firewall will update its activation status.


The Barracuda Web Application Firewall version 9.1.1 has the following important enhancements apart from bug fixes

  • Service Principal Configuration (SPN) has been moved from: "AccessControl->AuthenticationPolicies->Edit Authentication " to AccessControl->AuthenticationPolicies->Add/Edit Authorization This enables the customers to use different domain SPNs for different applications configured under Authorization while using the same service. Previously, all the applications on a service, configured under Add/Edit Authorization had restriction to use only only one SPN (Whatever was configured in Authentication Service attached to the Authentication Policy).
  • The failure conditions during connection pool when the latencies with the servers are high, are logged
  • A new configuration option "Count Auth Response Codes" is added under Bruteforce Prevention module. When enabled, it will count all error response codes as failure responses, otherwise it will ignore '401' and '407' response codes while counting the error responses.
  • Extended match enhancement of the Client-IP header to support comma separated IP's Eg: (Client-IP eq,,
  • Introduced a new configuration "Detect Mouse Event" under both DDoS policy and WebScraping policy
  • The persistent cookie value that is used for load balancing, will be encrypted from now on.
  • API v3 now supports HTML encoded characters in filters.
  • Optimization to reduce the time taken to apply configuration with 2K+ URL profiles.
  • Start time of FTP of access logs and the frequency of FTP access logs are now synced to peer box if two WAFs are in cluster.
  • Version

  • Fix : A possible outage when SSL connections timeout in the middle of a response from the backend servers, is addressed
  • Fix : A possible outage when the backend servers respond with non standard response codes, is addressed
  • Fix : An inconsistency in the updating of the configuration and search results on the Basic->Services screen, is addressed
  • Version 9.1.0

    The Barracuda Web Application Firewall firmware version 9.1 has the following main features and fixes. For a longer version of the release notes, please click here

    • Security
      • Support for Volumetric DDoS prevention service
      • Proxy protocol support for both HTTP and HTTPS services
      • Whitelist feature for DDoS capabilities
      • Followup action for Allow Deny Rules
      • CAPTCHA responses are made non cacheable with inclusion of no-cache headers in the response
    • Management
      • Comprehensive API support for configuration of WAF objects and retrieval of logs and statistics
      • Internal LDAP users/groups in the clustered units are synchronized
      • System now generate SNMP Trap messages for data path failures i.e. if the system hangs, crashes or the link is down
    • High Availability
      • When deployed in a High Availability cluster, traffic will failover to the standby unit when memory utilization on the active unit exceeds 70%
    • Other Issues
      • SAML signatures can now be signed with RSA-256
      • The negotiated Cipher Suite for services and servers are now logged in System Logs
      • An issue that resulted in the reset of the admin password after establishing a support tunnel connection on newly deployed virtual machines, has been addressed

    Version 9.0.1

    The Barracuda Web Application Firewall firmware version 9.0.1 is a followup to 9.0.0, and has the following major changes

    • Enhancement : The Basic->Service page is enhanced to ensure a better usability experience, faster load and configuration updates
    • Enhancement : Barracuda Advance Threat Protection (BATP) is enhanced to scan when licenses are provisioned
    • Fix : URL paths in certain cases, were not inspected for attacks when the attack vector comes as a part of neither the base URL nor the query part. This is fixed
    • Fix : An issue which resulted in the proxy IP not getting logged properly for requests on a persistent connection, is resolved.
    • Fix : The URL with a query is redirected back to the same after successful CAPTCHA validation

    Version 9.0.0

    The Barracuda Web Application Firewall firmware version 9.0.0 is a major release with the following new additions to the firmware. For a longer version of the release notes, please click here

    • The version 9.0.0 supports hardware with multiple physical ports and also offers link bonding to maximize the throughput
    • Integration with Barracuda Advanced Threat Protection for advanced protection against malicious uploads
    • Integration with NG Firewalls in cloud deployment scenarios
    • Geo IP matching at the content rule level
    • Various enhancements and fixes to the 8.1.1 firmware based on customer deployments and user inputs

    Version 8.1.1

    The Barracuda Web Application Firewall firmware version 8.1.1, is a follow up to 8.1, and has the following main features and fixes. For a longer version of the release notes, please click here

    • Security
      • Ability to configure all IP reputation rules, including Geo IP rules, at the application level, to support rules based on X-Forwarded-For or other headers
      • Support for the macro for inserting hostname in redirect URLs for Allow/Deny Rules
      • Referrer header field values also supported by the Mask sensitive data feature
      • If the Web Firewall Policy binding in the rule group level is left empty, it would inherit the policy defined in the service level
    • Management
      • Custom date range filters added to the CPU and Memory Utilization reports. These reports are available under System Summary Reports.
      • Service Group filter added to Search on the Basic->Services page
      • Special characters allowed for LDAP passwords
    • Deployments
      • Azure Security Center : Added support for ARM templates for Tier 2 Integration
      • Azure Security Center : Integration with Logging and Reporting capabilities of the Azure Security Center
      • Amazon Web Services : Enhanced Bootstrapping capabilities using AWS CFT and using Barracuda Web Application Firewall templates and Barracuda Web Application Firewall configuration backups
    • Other Issues
      • Issues addressing possible CPU utilization spikes in the 8.1 firmware and optimization to reduce the memory footprint of the data path process during processing of HTTP or HTTPS requests

    Version 8.1

    The Barracuda Web Application Firewall firmware version 8.1 is a major release that introduces multiple product enhancements to security, access control and management capabilities. Some of the enhancements are highlighted below:

    • Enhanced Web Scraping Protection
    • Granular Binding of Security Policies
    • Support for AMQP formatting in Exported Logs
    • URL and Parameter Profile Optimization
    • Support for Auto-Scaling in AWS
    • SAN Certificate CSR
    • Support for JSON Key Profiles
    • Load Balancing across Server Name Resolution
    • Integration with Barracuda Vulnerability Manager, HPE Fortify OnDemand and HPE Fortify WebInspect Vulnerability Scanners Integration with Denim ThreadFix
    • Support for HTTP/2 and Websockets (BETA)
    • Redesigned BASIC > Services page to enhance scalability
    • Support for ActiveSync applications via the Web Application Firewall

    Version 8.0.1

    The Barracuda Web Application Firewall firmware version 8.0.1 is a maintenance release which has fixes for issues found in 8.0 GA release

    Version 8.0

    The Barracuda Web Application Firewall firmware version 8.0 is a major release which introduces multiple product security, access control, management, and usability enhancements. Some of these are highlighted below while the longer version of release notes is here

    • Security
      • JSON payload can now be inspected for attacks.
      • Attack patterns have been re-organized for better visibility and control.
      • Client certificate based authentication can be enforced for specific URL space.
    • Access Control Enhancements
      • Federated Authentication via SAML 2.0.
      • The Access Control policy capabilities have been enhanced to customize and configure the login/logout pages.
      • Ability to enforce Brute force policy for failed login attempts.
    • Centralized Management Service
      • Supports version 3.5.2 Barracuda Control Server.
      • Barracuda Control Server v3.5.2 provides:
        • Single login for managing multiple Barracuda Web Application Firewalls.
        • Ability to upgrade multiple systems from one window.
        • Ability to generate aggregated reports for multiple Barracuda Web Application Firewalls.
        • Mechanism to configure multiple Barracuda Web Application Firewalls through templates.
    • System Management
      • Logging and Reporting:
        • Multi-level drill down capability added in Reports module to assist in forensic analysis.
        • Composite and Classic views have been implemented in Access Logs and Web Firewall Logs.
        • Each log in Web Firewall Logs and Access Logs is associated with an unique ID.
          • Unique ID can be added to the response page using the response page macros.
        • Ability to set the time (in 24 hour format), day/date and schedule the report.
      • Support for IBM App Scan 9.x.
      • REST API for configuring Allow / Deny Rules.

    Version 7.9.2

    Notes on the Barracuda Web Application Firewall version 7.9.2:

    Change in behaviour:

    • Base64 decoding is not applied to the parameter value that adhere to Data URI scheme unless Base64 Decode Parameter Value is set to "Yes". [BNWF-19540]
    • The Barracuda Web Application Firewall now does not perform deep inspection on the content of the POST body that is in text/plain format. [BNWF-19281]

    Fixes and Enhancements

    • Enhancement: It is now possible to include or remove the "Timestamp" and "Unit name" fields in logs that are exported to the syslog server. [BNWF-19508]
    • Fix: Negative integer in the "Max-age" header value is now honoured by the Barracuda Web Application Firewall. [BNWF-19542]
    • Fix: Username can contain backslash (\) for RADIUS authentication. [BNWF-19543]
    • Fix: "Policy Fix" now creates a correct parameter profile for the parameter that contains a colon. [BNWF-19103]
    • Fix: After upgrade to, the cookies were modified or not displayed in Cookies Exempted on the SECURITY POLICIES > Cookie Security page. This issue is fixed now. [BNWF-18890]
    • Fix: Internal database for log storage has been resized in the Barracuda Web Application Firewall 360 and 460 to reduce RAM usage. [BNWF-19105]
    • Fix: Various fields of web firewall logs and access logs are normalized to handle multi-byte charsets and escape sequence characters, which caused issues when logs were exported to CSV format.[BNWF-19136] [BNWF-19683] [BNWF-19580] [BNWF-16619]
    • Fix: An upgrade in the Azure platform resulted in some rare outage issues. This has been fixed now.[BNWF-19200]
    • Fix: An issue with the process of firmware upgrade using offline mode, is resolved.[BNWF-19302]
    • Fix: A possible outage caused due to memory overrun while logging SSL protocol version, has been addressed.[BNWF-18993]
    • Fix: If the Header for Client IP Address is selected for a service, the Barracuda Web Application Firewall checks for the occurrence of the header till 64 HTTP headers, and picks the right client IP address. [BNWF-18950]
    • Fix: Virus detection feature is now available for A2 instances on Azure and Amazon Web Services. [BNWF-18922]
    • Fix: In Bridge mode, the services created in languages other than English now works as expected. [BNWF-18823]
    • Fix: The URL encryption issue is fixed to encode the URLs properly to handle spaces in between the URL path.[BNWF-17222]
    • Fix: When the requests do not match the configured response body rewrite rules, the response is not chunk encoded and connection is not closed for HTTP/1.1 requests by the Barracuda Web Application Firewall. [BNWF-19546]
    • Fix: If the file without name is uploaded through multipart/form-data and no virus is detected in the uploaded content, then the request is not logged in the BASIC > Web Firewall Logs page.[BNWF-19432]

    Version 7.9

    This release of the Barracuda Web Application Firewall is a major release which includes a number of usability, security and management features, some of which are highlighted below:
    • Security
      • Cryptographic encryption of selected URL spaces is now available
      • Cookie exemption can now include asterisk (*) wildcard character with the cookie name. [BNWF-592]
      • Enhancements to attackdef framework which include:
        • Active / Passive / Off control per signature
        • Definition updates can be automatically updated without requiring a restart of the system
        • Notifications in case of availability of new definitions
        • Tool to validate Regex patterns for attack types
      • Ability to view locked out clients in the Barracuda UI
      • CAPTCHA as a followup policy has now configuration options to deal with clients violating bruteforce policies
      • SSL improvements which include PFS support, SNI and recent vulnerability fixes for heartbleed and other CVEs on OpenSSL
      • Parameter names are now inspected for attacks in the request
    • Access Control
      • Multi domain support for LDAP & Kerberos
      • Support for Chained authentication (LDAP + RADIUS)
    • Management
      • A fresh new Barracuda User Interface
      • Availability of interface information on status page itself
      • Backend enhancements to logging to ensure more number of access and webfirewall logs reside on the system
      • Geo IP tagging of access and firewall logs
      • Enhancements to search functionalities, and ability to save the searches
      • Enhancements to reporting functionalities
      • A new notification framework which gives configurability on event thresholds, system and service related event notifications via email
      • Hit counts now available for url Allow deny rules
      • Password security policy can be enforced to the internal and external administrators configured on the ADVANCED > Admin Access Control page
      • A rework of the templating system to provide more flexibility
      • Improvements to REST API
    • Platform
      • Integration of cloud stuff into the main stream firmware

    Version (7.9 GA release)

    Notes on some known issues of Barracuda Web Application Firewall version
    • The upgrade to 7.9 may take more than 5-10 mins in some cases.

    Version 7.8.2

    Note: The 7.8.2 release has enhancements and fixes exclusively for the Barracuda Web Application Firewall Vx on Azure and AWS ONLY.

    Fixes and Enhancements

    • Enhancement: In the Azure cloud deployment, configuration amongst systems can be synchronized in a active/active cluster of two or more nodes. [BNWF-15475]
    • Enhancement: The Barracuda Web Application Firewall now supports REST based APIs for configuration of Services, Security Policies, Certificates and Clustering. [BNWF-15474]
    • In the Azure cloud deployment, the Virtual IP for services is fixed to the WAN IP address and cannot be changed
    • The "Allowed API IP/Range", "Operation Mode", "Addresses" and "Interface for System Services" modules are not available in the Barracuda Web Application Firewall Vx deployed on Azure and Amazon Web Services

    Version 7.8.1

    Fixes and Enhancements

    • Enhancement: New kernel for facilitating deployments of Barracuda Web Application Firewall in VM environments
    • Enhancement: Support for base64 decoding of parameter values before applying deep packet inspection
    • Enhancement: Support for normalization of Microsoft %u encoding scheme before applying deep packet inspection
    • Enhancement: Configurable status codes for Redirect action in Allow-Deny-Redirect screen
    • Enhancement: The CSRF token embedded in the form can have validity period/expiry time set when CSRF Prevention is set to "Forms" or "Forms and URLs".
    • Enhancement: Optimization of the configuration elements to facilitate faster configuration commits
    • Enhancement: An irreversible hash is performed on the user passwords including the admin password to ensure password secrecy in the system.
    • Enhancement: Automatic recovery from a Bypass state is now possible without the need for rebooting the appliance.
    • Enhancement: The domain information of the client is forwarded to the server along with the user credentials in the Basic Authentication Header when Send Basic Authentication is set to Yes (ACCESS CONTROL > Authorization).
    • Enhancement: Tor exit nodes can now be blocked from accessing services.
    • Enhancement: For MS LDAP authentication, if the server indicates an expired password, the Barracuda Web Application Firewall can redirect the user to reset it.
    • Enhancement: Redirect action can be configured as temporary redirect or permanent redirect resulting in the Barracuda Web Application Firewall using 301 or 302 response codes respectively.
    • Fix: The double decoding is now applied to URL before deep inspection.
    • Enhancement: IP Reputation Filter is now available in Bridge mode.
    • Fix: An issue with flow control in SSL layer, which may affect large size SSL transactions is addressed.
    • Fix: Cipher suite preference can now be enforced from the service rather than relying only on the client's preference.
    • Fix: Configuration rollbacks during "Policy Fix" operation in Web Firewall Logs has been fixed.
    • Change in behaviour: Henceforth, the attack definitions are not activated automatically until "Enable Auto Apply Attack Definition" is set to Yes on the ADVANCED > System Configuration page manually. This setting is implemented to ensure that the activation of definition can be carried out during the production maintenance window.

    Version 7.8

    This release of the Barracuda Web Application Firewall includes the following new features and fixes: [ For a detailed list of features and release notes please click here. ]
    • Security
      • DDoS Enhancements - The administrators can define policies on specific URL spaces to ensure the clients are challenged with a CAPTCHA to validate themselves in case the Barracuda Web Application Firewall detects them as suspicious. These challenges thwart the attempts of DDoS on process and memory intensive resources of the backend applications from bots and crawlers. This is available from the WEBSITES > DDoS Prevention page. In addition to this, the CAPTCHA challenges can also be set as a Follow Up Action to other attacks such as SQL Injection, etc via the Security Policies > Action Policy feature. This helps to detect and thwart attempts from automated tools to repeatedly scan the website for vulnerabilities and waste resources. For example, sqlmap tool scanning for SQLi will be blocked.
      • Barracuda Blocklist Integration - Barracuda Blocklist is an extensive IP reputation system that lists IP addresses that are open proxies or are botnet infected. The system relies on honeypots to flag both web and spam botnets, which are used interchangeably, depending on the need. Under a DDoS attack, these addresses can be blocked with a single click to deflate the attack, with a minimal false positive risk. This is available from the WEBSITES > DDoS Prevention page.
      • True File type checks for File Uploads - In earlier releases, file extension checks could be evaded on a file upload by changing the extension to match one of the whitelisted extensions. From this release, such evasions can be blocked by fingerprinting the file to establish its true MIME type and matching the type against a whitelist. For example, this prevents a hacker from changing a file extension from .exe to .doc and upload it, since it will be evaluated to application/octet-stream and blocked (assuming the later has not been added to the Allowed Mime Types on the WEBSITES > Parameter Protection page).
      • Kerberos Authentication - The AAA module has been enhanced to support Kerberos authentication to backend services like OWA, SharePoint etc using Kerberos. The front end authentication would be form based authentication while the back end uses the Kerberos protocol.
      • Clickjacking Protection - Clickjacking and UI redressing attacks can now be prevented by enabling Clickjacking protection from the ADVANCED > Advanced Security page.
    • Cryptography
      • SNI support - This release adds support for SNI (Server Name Indication ) extension to SSL. This is particularly useful in a virtual hosting scenario where organizations may have several domains hosted on a single server using the same IP address and each domain has a distinct SSL certificate.
      • CRL (Certification Revocation Lists) support - This has been added for client certificates. CRLs can be automatically retrieved over HTTP and can be updated periodically by the system.
      • Backup Enhancements - System backups can be now be done over FTPS.
      • Performance and Stability improvements - The SSL modules have been now rearchitectured to ensure higher transactions per second and throughput support with lesser memory footprint while cutting down the risks of possible race conditions in earlier releases.
    • Networking
      • Synchronization for Network elements - The following objects are now synchronized across the cluster: (1) VLANs (2) Static routes (3) Interface routes and (4) ACLs. Interfaces in Management network group will not be synced in cluster.
      • Backup Enhancements - NTLM V2 is now supported while taking system backup.
      • Deployment - System IP can now be on a VLAN interface.
      • Persistence Enhancements - The Load balancing module can use HTTP header based persistence for directing traffic to backend servers.
    • Usability improvements
      • Clients that have been locked out as a result of setting the Follow Up Action to Block Client, can now be unblocked manually by the administrator .
      • Preferences have been added for viewing parameter profiles on the WEBSITES > Website Profiles page.
      • In a clustered setup, Join Cluster operation is now available when the Failback Mode is manual. Earlier, it was only available in automatic mode.
      • NIC speed, duplexity and statistics can now be viewed and edited from ADVANCED > Advanced Networking, under the configuration for Network Group: System. This is only available when Show Advanced Settings is set to Yes under ADVANCED > System Configuration.
      • Access Logs now have a host filter.
      • Interface routes and Custom Virtual Interfaces can now be edited.
      • This release adds an option for a custom message on the login page to meet compliance requirements, e.g. FISMA requires federal systems to display an access notice on the login pages.
      • A new tool has been added to find out how an IP address is categorized in the Geo IP database.
      • The data path can be manually restarted after an attack definitions update.
    • Logging and Reporting
      • The logging module has been enhanced to integrate with IBM QRadar SIEM System.

    Fixes and Enhancements

    • Fix: The sensitive parameters in the query string are cloaked when a request matches the rule group. [BNWF-14641]
    • Fix: The encoded parameters in the URL are not decoded once the SSO Cookie Update Interval is triggered. [BNWF-14522]
    • Fix: Join Cluster operation does not remove Management routes on the secondary/backup device. [BNWF-14420]
    • Fix: Server Time field in access logs was not displaying proper time in some cases. Fixed now. [BNWF-14410]
    • Fix: Browsers cannot save the password for the auth login page automatically. [BNWF-14362]
    • Fix: CPU Utilization graph on the BASIC > Status page displays accurate value for the time scale "Month". [BNWF-14344]
    • Fix - Booting up issues on virtual machine instances installed on Citrix XEN Hypervisor have been fixed. [BNWF-14270]
    • Fix: The virtual IP address is not duplicated in the database after the firmware upgrade. [BNWF-13778]
    • Fix: An issue while filtering the logs (Web Firewall/Access/Audit Logs) using Time as an additional filter has been fixed. [BNWF-13691]
    • Fix - Local Host Map entries on the BASIC > IP Configuration page can now be bulk edited. [BNWF-13998]
    • Fix - The appliances that are not connected to the internet for activation can now be activated offline. [BNWF-13873]
    • Fix: Sensitive parameter names that needs to be masked can include colon (:) in it. [BNWF-14281]
    • Enhancement: Ability to have system IP address on a VLAN interface. [BNWF-5013]
    • Enhancement: Report graphs are now displayed with all legends in High Chart layout. [BNWF-14364]
    • Enhancement - The default access control login page for a service can be modified to include a descriptive text. [BNWF-13502]
    • Enhancement: The ACLs , routes for the management network are now synchronized as part of the configuration synchronization in a cluster. [BNWF-14453]
    • Enhancement: Response body rewrite is now performed for the content-type "application/x-java-jnlp-file" too. [BNWF-14608]
    • Enhancement: Remote Support can now be enabled through console to override the disable option set in web UI. [BNWF-14574]
    • Enhancement: Client IP address is logged in the System Logs when the verification of client certificate fails. [BNWF-14493]

    Version 7.7

    The firmware version 7.7 of the Barracuda Web Application Firewall is a major firmware release that enhances the security and networking related capabilities of the product. For a detailed list of features and release notes please click here. Here is an outline of some of the enhancements and features
    • Security:
      • Protection against slow client attacks
      • Blocking access based on Clients IP Reputation: This version provides an easy way to block out clients based on Geo Location tag for that IP address
      • Armored browser integration: Barracuda Web Application Firewall now integrates with armored browser from Protect On Quarri to extend the security cover to the client side as well
      • Enhancements to shared security policies: CSRF can be enabled using the shared security policy. Max instances check for parameters which prevent a class of HTTP Parameter pollution attacks, is enhanced for wild card parameter profiles. Administrators can now change the system generated tokens such as ncforminfo, BNES_ or BNIS_
    • Networking:
      • Advanced routing capabilities: The virtual site can be used as a networking entity which has its own routing tables, ACLs, using which, the services on WAF can be grouped by their own routing requirements.
      • Network ACLs: Network ACLs can now be configured for traffic that is being NATed or proxied via the WAF.
    • Deployment:
      • Active-Active HA: Two WAFs in a clustered environment, can be configured to have active services on them, and failover/failback if one of the units fail.
      • Stability and improvements of the IPv6 functionalities.
    • Usability improvements:
      • Integration with Cenzic for vulnerability patch management
      • Bulk edit for Services page
      • Persistence of node expansion state in Basic -> Services screen
    • Logging and reporting enhancements
      • Service level SNMP stats: The SNMP MIB has been enhanced to support multiple statistics at the application level
      • System Logs, like the server "up" and "down" events etc are now available in the UI
      • Syslog NG integration
      • Integration with Splunk and Arcsight now available

    Version Maintenance GA release)

    Notes on differences between Barracuda Web Application Firewall version and
    • Enhancement: Support for Private Interfaces in a VSITE to support enhanced backend traffic routing.
    • Fix: A bug in the event manager which resulted in logs not getting displayed correctly on 32 bit machines, is fixed.
    • Fix: The administration access to MGMT port is now enabled by default.
    • Fix: A possible race condition in the siteminder authencation module is addressed.
    • Fix: A possible memory overrun in one specific path of the HPP feature of the security module is addressed.
    • Case IDs addressed: 01206948, 01204338, 01204381, 01205421, 01206972, 01206766, 01222910, 01222697, 01226460.

    Version (7.7 Maintenance GA release)

    Notes on differences between Barracuda Web Application Firewall version and
    • Enhancement: The API interface is enhanced for better usability.
    • Enhancement: The Instant-SSL functionality is now supported in bridge mode of operation too.
    • Enhancement: SMS passcode feature is enhanced to support configuration of custom access challenge URL.
    • Enhancement: SMS passcode feature is enhanced to support sharing of the password with the backend during two factor authentication.
    • Fix: CVE-2012-4929, CVE-2012-4930 on the possible vulnerability to SSL/TLS CRIME attack is addressed.
    • Fix: A bug leading to offline upgrade taking upto 15 minutes, is resolved.
    • Fix: A possible memory overrun in the HPP feature of the security module is addressed.
    • Fix: Extended match for Websites->Allow/Deny rules will now accept Client networks in the Client-IP macro.
    • Fix: Bulk edit of Websites->Web Site Translations now retains the context chosen in the filter.
    • Fix: A possible bug in editing of services which are on a VLAN in bridge mode, is fixed.
    • Fix: A bug in Basic->Reports which causes issues with emailed reports when a filter is chosen, is fixed.
    • Fix: Characters such as '$','@' and '#' are allowed as sensitive parameters under Mask Sensitive Data.
    • Fix: A bug in LDAPS authentication when Role Based Administration is used, is fixed.
    • Case IDs addressed: 01169601, 01174363, 01175945, 01178013, 01179067, 01179965, 01178013, 01180787, 01182087, 01184134, 01194198.

    Version (7.7 GA release)

    Notes on the Barracuda Web Application Firewall version
    • The Barracuda Web Application Firewall has auto created DENY-ALL rule. While auto acls are created to take care of most of the functionalities that need acls, please ensure that you create allow network acls in case a functionality needs some ports to be open and are not auto created already.
    • A window of downtime is needed when upgrading a cluster from 7.6.4 GA release to 7.7 or when planning a "join cluster" activity in 7.7. It is recommemded to contact Barracuda support if you are upgrading a clustered setup from 7.6.4 GA to the 7.7 release when the failback mode is Automatic
    • When upgrading 7.6.4 GA to in a clustered environment, its recommended that the failback mode is "Manual" and the standby unit is upgraded first.
    • In a clustered environment, some config changes may take a little longer to complete., for eg: Creation of VSITE may take one minute or more
    • When planning a revert in a clustered environment, it is recommended to revert both WAFs to the 7.6.4 during a planned downtime.
    • Configuration changes will not be synchronized to the peer WAF when the peer is not in the same firmware version as the WAF on which the configuration change is being done. A heterogenous mode which has two WAFs in two different firmware versions is hence not recommended.
    • Policy wizard fix for shared security policy checks on CSRF is not yet available
    • Functionalities like GeoIP tagging, and HA Active-Active, are not supported in bridge mode. Please contact Barracude Technical Support when using in bridge mode of deployment
    • Upgrade from to in bridge mode on older machines with 32 bit kernel needs help from Barracuda Tech Support. This is usually serial numbers below 210000

    Version 7.6.4

    • Fixes for provisioning and licensing issues with VM version of the Barracuda Web Application Firewall
    • Support for the firmware to work with Barracuda Web Application Firewall Model 963
    • Feature: Backups taken on Barracuda Web Application Firewall can be chosen to be in encrypted form

    Version (7.6.4 GA release)

    Notes on the Barracuda Web Application Firewall version
    • Fix: The issue of potential false positives that could be triggerred during CSRF checks in case the token is not found at the end of param list, is addressed
    • Fix: OCSP validation failures in certain cases of leaf certificates, is addressed
    • Fix: SNMP get for service status, which could give incorrect result, is fixed
    • Enhancement: Session recording limits are relaxed to capture more sessions. The UserID filter is also fixed to work in siteminder deployments
    • Fix: An issue with incorrect handling of radius attributes, leading to radius login failures, is fixed.
    • Enhancement: NTP time synchronizaion events are logged now
    • Enhancement: Support for long FTP welcome banners in ftp proxy
    • Fix: Rollbacks seen due to duplicate parameters and missing parameters
    • Fix: A few issues in session recording feature, like the failure to capture inserted or rewritten headers, are fixed
    • Change in Behaviour: When website translation rules are configured, the Set-Cookies which contain explicit Path attributes, will not be subjected to the translation
    • Case IDs addressed : 01018200, 01058921, 01068508, 01070934, 01079598, 01084938, 01092296
    • Known issue: An occasional error, which would indicate a concurrent session is in progress, may appear during certain configuration operations like breaking a cluster. The configuration does take effect in such a case, but a refresh of the Barracuda Web Application Firewall UI page is recommended in case this error is seen.

    Version 7.6.3

    • Siteminder enhancements, V12 SDK integration, customized extended timeouts.
    • Enhancements to request, response header and body rewrite rules.
    • Other enhancements and bug fixes from the version 7.4.5 merged to 7.6.3
    • DNS configuration support for Admin Access control for External Authentication services
    • Various miscellaneous UI enhancements for better presentability
    • Fixes: Avoiding HTTP 302/307 responses during session validation timeouts to ensure POST requests with valid sessions do not fail.

    Version (7.6.3 maintenance GA release)

    Notes on the Barracuda Web Application Firewall version
    • Fix: The upgrade of the Barracuda kernel was failing on a few older 32 bit platforms. This is addressed in this release
    • Fix: A possible race condition in the data path leading to a leak of sockets and thus memory, is addressed
    • Fix: A potential configuration rollback during a Policy Tuner fix of webfirewall logs generated due to parameter profiles, is addressed
    • Fix: In some configurations, it was possible that the status page inaccurately shows the number of active servers being higher than the total number of servers configured in the system. This issue is addressed
    • Fix: A possible path in Cross Site Resource Forgery checks, may result in the Barracuda Web Application Firewall reporting false positives on CSRF checks. This has been addressed.
    • Fix: A potential race leading to a high CPU usage from the data path in processing socket events is addressed
    • Fix: If the Barracuda Web Application Firewall UI administration is configured to be on the MGMT interface, a potential issue was causing the UI to be lost after the upgrade. This is addressed in this release
    Notes on the Barracuda Web Application Firewall version
    • If a backup taken on 7.4.x firmware is restored onto another 7.4.x firmware, it is possible that some passwords will need to be recreated (for example, the external LDAP password, or the FTP server password in ADVANCED > Export Logs).
    • After an upgrade from 7.5 (or earlier) firmware to 7.6 firmware, the logs stored on the disk will be cleared and backed up to a different directory. It is recommended that all logs be saved before an upgrade. Barracuda recommends exporting the logs to a syslog server as a best practice.

    Version 7.6

    This release of the Barracuda Web Application Firewall includes the following new features and fixes:
    • Vsites to group the services, Allow/Deny rules, Advanced security policies, Web Site Profiles and Web Site Translations.
    • Enhancements to the BASIC > Status page (Dashboard) to have custom graphs and trending on CPU and memory utilizations.
    • Enhancements to the UI components for better presentability in key screens like BASIC > Services, Allow/Deny rules etc.
    • Most of the screens are now available for configuration and monitoring via Barracuda Cloud Control.
    • Ability to push configurations related to Default security policy and Attack patterns across multiple Barracuda Web Application Firewalls via Barracuda Cloud Control.
    • Various web application firewall features are now IPv6 aware, thus enabling firewalling and deep packet inspection of web apps hosted on IPv6 addresses - available in expert mode and as a beta stage since some aspects may need assistance from Barracuda Support.
    • Few important bug fixes related to the handling of issues related to SSL traffic, which includes rare and occasional loss of SSL connections from the clients.
    • More robustness is built into the monitoring of cluster related modules thus avoiding few stability concerns seen in previous releases. The issue of unexpected failover to the secondary box due to false alarms triggered during certain operations in a cluster mode is also taken care in this version.

    Version (7.6 GA release)

    Notes on the Barracuda Web Application Firewall version
    • After an upgrade from 7.5 or previous releases to the, the logs stored on the disk will be cleared and backed up to a different directory. It is recommended to save the logs before an upgrade. Barracuda recommends exporting the logs to a syslog server as a best practice.
    • The status page graphs may occasionally not reflect the real traffic statistics for IPv6 services.
    • While navigating across tabs in the Barracuda Web Application Firewall GUI, if a blank page is encountered, it is advised to reload the page or revisit the screen.
    • After configuring both IPv4 and IPv6 services in a single Barracuda Web Application Firewall, if any subsequent change is made in BASIC > IP Configuration screen, an explicit "Reload'' is needed to have the services working again.
    • When creating IPv6 servers, ensure that an appropriate route to these servers exists by creating appropriate IPv6 address on LAN or WAN interface.
    • The "tcpdump'' functionality which is available via the ADVANCED >Troubleshooting screen, works reliably for IPv4 addresses only.
    • Syslog settings, if chosen via ADVANCED > Export Logs, may have to be recreated after an upgrade to 7.6 from the previous version of the firmware.
    • When using non-default certificates for Secure Administration (HTTPS) of the UI, there are known issues with backup and restore and upgrade. Barracuda recommends using the default (Barracuda) certificate during these operations. After the successful completion of these operations, you can re-apply your certificate.
    • There are known issues in restoring a backup containing both IPv4 and IPv6 services. Please contact support for assistance, if required.
    • Reverting the firmware from 7.6 version to the 7.5 version puts the old IP on the MGMT configured before the upgrade to 7.6, if a new one was used after the upgrade to 7.6