10.5.0 Release Notes

What's New in Version 10.5.0

SecureEdge version 10.5.0 is a major release. It contains new features and several important fixes.

Important Notes before Updating

Configuration Option for a Report Banner

It is now possible to customize the branding for reports and also to add a small text to the footer.

Open

Display Item for Safe Search in DNS Logs

A label for Safe Search is now displayed in the list for DNS logs if they have been enforced.

Open

Traffic Classification Categories for AI

Traffic classification categories have been updated and now include new tools like AI.

SNAT Policies

Site Source NAT

The Barracuda SecureEdge Manager allows you to create Source NAT (SNAT) policies for your connected Sites. Key highlights include:

• The scope of the rule All Sites or of a specific Site can be selected.

• Options are provided for a rule's priority level: Real Time, High, Medium, and Low.

• The fallback actions Allow and Block are provided when the rule cannot be applied.
  
  

  Open

  

For more information, see How to Create Site Source NAT Rules.

Edge Service Source NAT

You can now create Source NAT (SNAT) policies for your connected Edge Services. Select either All Edge Services or a specific Edge Service as the scope of this rule.

Open

For more information, see How to Create Edge Service Source NAT Rules.

Ingress NAT Rule on TCP Port 443 Triggers Warning

The warning message is displayed for an ingress NAT rule configured with destination criteria on TCP port 443.

Open

For more information, see Ingress NAT Rule on TCP Port 443 Triggers Warning.

Enable TCP Transport

You can enable TCP transport on a SecureEdge Site or Private Edge Service. Note that enabling TCP transport will disable SD-WAN optimization.

Open

For more information, see How to Enable TCP Transport for VPN Tunnels to the Edge Service.

Resolved Bugs and Improvements in Release 10.5.0

SecureEdge Edge Service

• Resizing the throughput of the SecureEdge Edge Service no longer breaks the ruleset and resolves DNS resolution issues. [BNNGF-100077]

WAN Hub

• SecureEdge integration no longer deletes the appliance configuration when the Cloud service temporarily returns an invalid response.  [BNNGF-99674]

• The automatic cleanup of HA configurations has been removed when the SecureEdge cloud service returns an empty response, thereby preventing accidental disruptions of working HA setups.  [BNNGF-99864]

• The default values for the BGP service is now written correctly for SecureEdge.  [BNNGF-100013]

Known Issues 10.5.0

General Known Issues

• ACL Rule – Setting up the source or destination criteria to all Sites and Private Edge services results in the same networks configured on the box. [SWCS-3988]

• Dashboards – For SecureEdge appliances running version < 9.0.3, adding more than one filter can keep the other filter(s) from being applied or might return no results.

• Identity Management – The Barracuda SecureEdge Identity app for Google Workspace is currently awaiting official approval from Google.

• SIP – The use of a SIP proxy with SecureEdge might still require manual adjustments in the configuration files depending on the SIP setup. [BNNGF-95603]

• Proxy Connect – Proxy Connect block pages are not visible to the end user. [BNNGF-96048]

• Proxy Connect – Proxy Connect fails when the Action is set to Alert/Warn in Web Filter policies. [BNNGF-96138]

Known Issues Related to Azure Log Analytics (OMS)

• On boxes with Azure Log Analytics (OMS) activated, the phibs service does not restart automatically after update. To get the service running, a reboot is required.