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

10.0.1 Release Notes

  • Last updated on

What's New in Version 10.0.1

SecureEdge version 10.0.1 is a minor release. It contains new features and several important fixes.

TLS Interception Certificate

TLS Inspection has been simplified with a new feature that provides a self-signed certificate for each workspace. You can create, edit, delete, or download certificates as needed. For more information, see SSL Inspection.

certificate.png
New Predefined Custom App: M365 Conditional Access

Each new SecureEdge account or workspace includes a predefined custom application called “M365 Conditional Access”. For more information, see Microsoft 365 Conditional Access Deployment.

ma-365.png

“All Users” Toggle for ZTNA Policies

You can now enable all users for a ZTNA policy to match other policies in which the User/Group is a source or access criteria. For more information, see Zero Trust Access Policies.

all-users.png
Support for WCS 3.3 Additional Categories

SecureEdge now includes the following new categories:

Category

Super Category

Code Repositories

Technology

Cheating

Illegal or Improper

Artificial Intelligence

Technology

Hosted Payment Gateways

Commerce and Shopping

For more information, see Secure Web Gateway (SWG)

VLAN Support on WAN Bridge Configuration

You can add a VLAN tag to the bridge WAN configuration. For more information on LAN-VLAN deployments, see How to Create an Inline Bridge on a Stand-Alone Site.

wan-bridge.png

Important Announcements and Notes for Release 10.0.1

The existing SecureEdge Access subscription has been renamed to SecureEdge Private Access.

Resolved Bugs and Improvements in Release 10.0.1

Barracuda OS
  • SecureEdge now supports additional WCS 3.3 categories. [BNNGF-95628]

Authentication
  • The configuration issue when re-enabling SSL Inspection with a different CA on SecureEdge appliances has been resolved. [BNNGF-97636]

  • An issue has been fixed where users sporadically lost access to their ZTNA resources. [BNNGF-98480]

  • A new toggle “All Users” has been added to ZTNA policies to apply settings to all users. [SWCS-5411]

Firewall
  • ZTNA policies are removed as expected when removing a CGF from SecureEdge. [BNNGF-95066]

REST
  • HTTP/1.1 sessions with "Connection: close" and without Content-Length or Transfer-Encoding are now handled correctly. [BNNGF-97182]

  • SecureEdge block pages now look have a refreshed design for easier use. [SWCS-5506]

  • Each new SecureEdge account or workspace includes a predefined custom application called “M365 Conditional Access”. [SWCS-5456]

VPN
  • An issue has been fixed where pre-allocated SPI structures in the VPN server were not being properly released due to incorrect error handling. [BNNGF-96820]

SecureEdge SaaS Subscription
  • The SecureEdge Access subscription has been renamed to SecureEdge Private Access. [SWCS-5352]

Known Issues 10.0.1

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 still might 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.