Security & Backup

Barracuda Email Gateway Defense

Check Barracuda Email Gateway Defense account status, domains, and mail stats - and clean up phishing across every mailbox.

Dex connects to Barracuda Email Gateway Defense (EGD, formerly Essentials / Email Security Service) so admins can check an account's status, review protected domains and their verification state, and read inbound and outbound mail statistics. With Barracuda Incident Response, Dex can review what users reported as suspicious and run a phishing clean-up that quarantines the matching email across every mailbox of the customer's Microsoft 365 or Google Workspace tenant. Available as an MSP global app: one shared Barracuda Token Service application covers every managed account, and each Dex tenant is confined to its numeric Barracuda Cloud Control account id. Reads only, plus a single approval-gated incident write that never permanently deletes mail - policy, quarantine release, message log, allow/block lists, and users stay in the Barracuda console.

Start free →

What Dex does with Barracuda Email Gateway Defense

Dex handles both admin workflows and employee self-service — all policy-guardrailed and audit-logged.

For admins (Dex Pro)

Read an account's Barracuda Email Gateway Defense status - and flag SUSPENDED or DISABLED accounts as urgent
List protected domains and report any that are UNVERIFIED or DISABLED
Read inbound and outbound mail statistics per account or per domain - allowed, blocked, deferred, quarantined, by action
List the Microsoft 365 / Google Workspace tenants connected to Barracuda Incident Response
Review emails this customer's users reported as suspicious
Run a phishing clean-up incident that quarantines (or only reports) matching mail across every mailbox - with approval, never a permanent delete
List past Incident Response incidents and read their remediation counts
Deploy as an MSP global app - one shared BTS application, each customer confined to its numeric Barracuda Cloud Control account id

Just ask Dex

Your team types a request in plain language. Dex investigates, plans, and executes — with the right guardrails.

Admin prompts

>Is Contoso's Barracuda Email Gateway Defense account active, and are all its domains verified?
>Show me the inbound mail stats for contoso.com over the last 7 days - how much was blocked or quarantined?
>What have Acme's users reported as phishing in the last week?
>Everyone at Contoso got a phishing email from billing@example.com with subject "Invoice overdue" - quarantine it across all mailboxes
>Did that phishing clean-up incident finish? How many emails were remediated?

Policy actions

Every action Dex can take on Barracuda Email Gateway Defense is declared, scoped, and guardrailed. Admins control which apply, who approves them, and whether they're limited to self-service.

Action	What it does	Guardrails
`barracuda_egd_list_accounts`	List every Barracuda Email Gateway Defense account the MSP manages (MSP master connection only)	—
`barracuda_egd_get_account`	Read the Barracuda Email Gateway Defense account status for this customer	—
`barracuda_egd_list_domains`	List this customer's domains and their verification state	—
`barracuda_egd_get_domain`	Read one Barracuda Email Gateway Defense domain for this customer	—
`barracuda_egd_get_account_statistics`	Read inbound and outbound mail statistics for this customer's account	—
`barracuda_egd_get_domain_statistics`	Read inbound and outbound mail statistics for one of this customer's domains	—
`barracuda_egd_list_ir_accounts`	List every Barracuda Incident Response account the MSP manages (MSP master connection only)	—
`barracuda_egd_list_ir_tenants`	List this customer's Microsoft 365 / Google Workspace tenants connected to Barracuda Incident Response	—
`barracuda_egd_list_incidents`	List this customer's Barracuda Incident Response incidents	—
`barracuda_egd_get_incident`	Read one Incident Response incident and its remediation counts	—
`barracuda_egd_create_incident`	Create a phishing clean-up incident that quarantines (or only reports) matching emails across this customer's mailboxes; never deletes	approval
`barracuda_egd_list_user_reported_emails`	List emails this customer's users reported as suspicious	—

How to configure Barracuda Email Gateway Defense

Onboarding takes minutes. Dex validates your credentials before saving them.

Setup steps

1
In Barracuda Cloud Control, register a Barracuda Token Service (BTS) application under a user with Email Gateway Defense administrator rights over the managed accounts.
2
Grant the application the scopes Dex needs: ess:account:read, plus forensics:account:read and forensics:account:write for Incident Response phishing clean-up.
3
Note your region (us or uk) and, for each managed customer, the numeric Barracuda Cloud Control account id from GET /beta/accounts/ess on the MSP master.
4
In Dex, enable the Barracuda Email Gateway Defense integration and paste the Client ID and Client Secret; leave account_id blank on the MSP master.
5
Dex exchanges the credentials for a token and validates the connection before saving. For MSPs, map each customer tenant to its account_id.

Vendor documentation ↗

Credentials required

client_id: BTS application Client ID (secret-handled; never surfaced)
client_secret: BTS application Client Secret (secret; never surfaced)
region: Barracuda region - us (default when blank) or uk
account_id: This tenant's numeric Barracuda Cloud Control account id - leave blank on the MSP master, set it on the customer connection once discovered (per-customer MSP isolation)

Requirements

•A Barracuda Cloud Control account with Email Gateway Defense administrator rights and a registered BTS application
•Incident Response requires the forensics scopes and an Email Protection plan that includes it (the legacy Advanced plan lacks it)
•Reads only, plus one approval-gated incident write limited to QUARANTINE or NONE - never a permanent delete
•Message log, quarantine release, policy, allow/block lists, and user management stay in the Barracuda console (no public API)
•For MSPs, deploy as a global app with per-customer account_id scoping