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

How to Configure SecureEdge Access

  • Last updated on

The Barracuda SecureEdge Manager allows administrators to configure SecureEdge Access either via Barracuda Cloud Control or by syncing user directories via Identity Service with the Zero Trust Access service and defining various parameters such as point of entry, custom client network, and DNS suffix in client networks. SecureEdge Identity Service supports the following user directories: Microsoft Entra ID, LDAP, Google Workspace, Okta, and Barracuda Cloud Control. SecureEdge Access lets you implement secure access to internal and external enterprise resources, whether they are on-premises or in the cloud, by using a Zero Trust endpoint solution known as the SecureEdge Agent. Barracuda SecureEdge Access brings Zero Trust access service to your endpoint with a quick and easy configuration. SecureEdge SaaS Edge Service and SecureEdge Access are subscriptions hosted and managed by Barracuda Networks. You can activate SecureEdge Access using a product activation key. For more information on how to activate SecureEdge Access, see How to Activate the Edge Service and SecureEdge Access Using an Activation Key.

Before You Begin

SecureEdge Access Deployment

Configure SecureEdge Access with the following steps:

Step 1. Activate SecureEdge Access Using Activation Key
  1. After your order is placed with Barracuda Networks, you will receive an email from Barracuda Customer Services with a product activation key. In the Product Key section, click Activate

  2. Log in with your Barracuda Cloud Control account.

  3. Complete the 4-step product activation process.

    sel-country.png

  4. Accept the license agreement to complete the subscription. Your product subscription is activated as soon as the activation procedure is complete. 

After accepting the terms, you are directed to the SecureEdge dashboard. You can verify your subscriptions in the SecureEdge Manager via Profile > Subscription. You can proceed with Step 2.

Step 2. Points of Entry

Barracuda SecureEdge supports three different types of points of entry: firewalls, edge services, and sites. The SecureEdge Manager allows you to configure the points of entry by selecting either an existing edge service, site, or firewall that the Barracuda SecureEdge Agent can connect to. Registration of CloudGen Firewalls is token based. The CloudGen Firewall fetches a requisite certificate and a zero trust access policy from the cloud services; however, it does not get security features or SD-WAN policies from the service. On the Points of Entry page, you can find information on enrolled points of entry in the Barracuda SecureEdge environment.

To select the CloudGen Firewall as a point of entry, you must first configure a CloudGen Firewall in Barracuda SecureEdge. For more information, see How to Configure a Barracuda CloudGen Firewall in Barracuda SecureEdge.

PoE.png

For more information, see How to Configure Points of Entry.

Step 3. Connect to Identity Service

The Barracuda SecureEdge Manager allows you to configure an identity provider as well as user directory via the Identity > Settings tab and sync with Zero Trust access. With Identity Service, you can enroll users/groups with their respective devices to create secure remote access to internal and external enterprise resources, whether on-premises or in the cloud with a quick and easy configuration via the SecureEdge Access Agent. For more information, see Identity Service.

google-ws.png

The Barracuda SecureEdge Manager supports the following identity providers and user directories:

Identity Providers

User Directories

Barracuda Cloud Control

Barracuda Cloud Control

Microsoft Entra ID

Microsoft Entra ID

Google Workspace

Google Workspace

OpenID Connect

Okta

SAML 2.0

LDAP

Email

Step 4. SecureEdge Access Global/Default Settings

You can configure SecureEdge Access settings on a global level and define various parameters such as Tamperproof, Device Pre-Logon, User Device Limit, Web Filtering, and DNS suffix in client networks. In addition, you can also configure a custom client network configuration.

access-global-settings.png

For more information, see How to Configure SecureEdge Access Global Settings.

For more on SecureEdge Access Agent network configuration, see How to Configure a SecureEdge Access Agent Network.

For more information on LDAP and Microsoft Entra ID, see LDAP Active Directory and Microsoft Entra ID.

Step 5. Enroll Users

The Barracuda SecureEdge Manager allows you to enroll users. A single user can enroll multiple devices on the same token. On the Users page, you can find detailed information on enrolled users.

access-users.png

For more information, see How to Enroll Users in Barracuda SecureEdge.

Step 6. Verify Enrolled Devices and Users

The Barracuda SecureEdge Manager allows administrators to enroll users with their respective devices. After the enterprise enrollment process is completed, your device protection will be automatically enabled. On the Devices page, you can find detailed information on enrolled devices.

enrolled-devices-page.png

For more information, see How to Verify Enrolled Devices and Users.

Step 7 Create a Zero Trust Access Policy

The Zero Trust Access policy defines the resources made available to end users of the Barracuda SecureEdge Agent and the associated access restrictions. The Zero Trust Access page displays all defined policies with respect to your selected workspace.

ZeroTrustAccess.png

For more information, see Zero Trust Access Policies.

Additional Information

To add a Zero Trust Access Policy for Zero Trust Access to reach a website for which no pre-defined apps exists (for example, zoom.us, msn.com, microsoft.com, tiktok.com, or whatsapp.com), you must define a custom web application. However, this overwrites the ‘non-interceptable’ property that states that SSL Inspection should not inspect such a website. In this case, you must configure an SSL Inspection rule with the respective client network as source and a custom web application as destination, and set SSL Inspection for these websites to Do Not Inspect.