How to Configure Agent Based DNS Access in SecureEdge
Agent-based DNS Access enforces web filtering and AI security policies on individual devices by installing the Barracuda SecureEdge Access Agent. This article explains the manual setup: configure an identity provider, create a local user, set web filtering and AI access policies, enroll the user, and activate the agent on the device.
This procedure uses a local user for demonstration purposes. In your environment, you should configure an Identity Provider (IdP) and user directories on the Identity > Settings page in SecureEdge Manager to synchronize and manage users and groups.
Before you begin
You must have a SecureEdge DNS Access license and administrator access to the SecureEdge workspace. For more information, see How to Activate the Barracuda SaaS Service Using an Activation Key.
When using Email Identity Provider authentication, each user must have a valid email address and access to the corresponding mailbox to receive authentication emails.
Step 1: Configure Email as the Identity Provider
Email authentication is the simplest way to get started. For production deployments, integrate with a supported Identity Provider, such as Microsoft Entra ID, to simplify user management and authentication. For more information, see SecureEdge Identity Management.
Email is the simplest identity provider (IDP) to configure for a quick setup. SecureEdge sends a one‑time verification code to the user's email when they authenticate the agent. Go to Identity > Settings and add Email as an Identity Provider. Verify that Email appears in the Identity Provider table.
For more information, see How to configure an identity provider.
Step 2: Create a Local User
Local users are recommended only for testing and evaluation purposes. For production deployments, configure directory synchronization with your identity provider (IdP) to automatically manage users and groups.
Create a local user account you want to enroll. The email address entered here must match the address used for agent authentication. Go to Identity > Users and add a local user. You must add a user with the email address you want to use for logins. Verify that the new user appears in the Users table.
For more information, see How to Create Local Users or Groups.
Step 3: Create a Web Filter Policy
Go to Security > Web Filter > Policies. Create a Web Filter policy with the All Sources scope to apply a baseline URL filtering posture across your enrolled users. Select the URL categories to block or allow based on your organization's requirements. For an overview of all policy scopes and options, see Web Filter Policies.
For step-by-step instructions, see How to Configure a Web Filter Policy.
Step 4: Review AI Tool Usage in the AI Tools Inventory
Block all AI Tools, then Allow Approved Tools
Go to AI Security > AI Tools Inventory. The AI tool inventory page opens.
On the AI tools inventory page, click the checkbox at the top of the AI Tools table to select all rows.
In the bulk-action bar that appears, set the status to Block. All detected AI tools are now blocked for your network.
To allow a specific approved AI tool, search the table, e.g., Copilot.
In the Status column for that tool, click the drop-down and select Allowed.
Repeat for each additional tool your organization approves.
The status change is enforced through your Web Filter policies. Tools set to Allowed are accessible to users; tools set to Blocked return a block page. Tools that remain Unreviewed are not covered by an AI security rule and fall through to the Web Filter default action. For more information, see AI Security in SecureEdge.
Step 6: Create a User Enrollment Invitation
An enrollment links the local user you created in Step 2 to a license and device profile, and generates an invitation link that is sent to the user by email.
Go to Access > Enrollments.
On the Enrollments page, click New Enrollment in the top-right corner and select Users.
The New Enrollment window opens. Specify values for the following:
License and seats – Select DNS Access.
Enrollment profile – Select Managed.
Enrollment invitation – Search for and select the local user created in Step 2.
Send email to the users – Enable this toggle. The user will receive an enrollment invitation email.
Click Create Enrollment.
The Enrollment Created window opens. Click Copy Managed link to save the enrollment link. Click Close.
The enrolled user now appears in the Enrollments table.
For more information, see How to Enroll Users.
Step 7: Enroll Users Using the SecureEdge Access Agent
Download and install the Barracuda SecureEdge Access Agent. The user completes enrollment on their device using the invitation email from step 6.
Open the enrollment invitation email with the subject You have been invited to SecureEdge and click Enroll now.
If the SecureEdge Access Agent is not yet installed, click Download now and install it on the device.
Once installed, click Open SecureEdge. The Enterprise Enrollment page opens in the agent. Click Accept.
On the Authenticate page, click Authenticate. Enter the email address used for enrollment and click Continue.
A verification code is sent to the user's email address. Enter the code and click Continue to verify identity.
The SecureEdge Access Agent Activity page opens, confirming the device is enrolled. Enable the Protection toggle to activate filtering. The status indicator turns green when protection is active. For more information, see Barracuda SecureEdge Access Agent.
Go to Access > Enrolled Users or Access > Enrolled Devices to verify enrollment in SecureEdge Manager.
For more information, see Enrollments.
(Optional) Verify AI Tool Enforcement in AI Risk Logs
After updating AI tool statuses, review AI Risk Logs to confirm policy enforcement.
Go to Reports > Logs > AI Risk Logs. For more information, see SecureEdge Logs.
To create a AI Risk report, go to Reports > Reports > AI Risk Overview. Schedule this report daily, weekly, or monthly and send it to an admin or manager to Monitor AI usage in the network and Shadow AI's impact on your security posture. For more information, see SecureEdge Reports.