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

Login Sign Up Contact & Support

United States – English (GMT-5)

Email Security Gateway

Forensics & Incident Response

Message Archiver

Cloud Archiving Service

Total Email Protection

CloudGen Firewall

Firewall Insights

NextGen Firewall X

Network Access Client

Web Security Gateway

Web Security Agent

Web Application Firewall

WAF Control Center

WAF-as-a-Service

Vulnerability Manager

Vulnerability Remediation Service

Active DDoS Prevention

Load Balancer ADC

Cloud Security Guardian

Reporting Server

Cloud-to-Cloud Backup

Managed Workplace

Intronis Backup

Reference / FAQ

TechSummit 2019

Barracuda Web Security Gateway

Overview Documentation Training Certification Materials

Email Security Gateway

Forensics & Incident Response

Message Archiver

Cloud Archiving Service

Total Email Protection

CloudGen Firewall

Firewall Insights

NextGen Firewall X

Network Access Client

Web Security Gateway

Web Security Agent

Web Application Firewall

WAF Control Center

WAF-as-a-Service

Vulnerability Manager

Vulnerability Remediation Service

Active DDoS Prevention

Load Balancer ADC

Cloud Security Guardian

Reporting Server

Cloud-to-Cloud Backup

Managed Workplace

Intronis Backup

Reference / FAQ

TechSummit 2019

Login Sign Up Contact & Support

United States – English (GMT-5)

Back to Knowledgebase

Why Traffic from Microsoft Edge Not being Filtered using WSA with WSG

Type: Knowledgebase
Date changed: one year ago

Solution #00007855

Scope:

All Barracuda Web Security Gateways.
Setting up a WSA for remote filtering with WSG

Answer:
Add Microsoft Edge browser to Advanced >> Remote Filtering tab (Applications to Filter (All Ports))
Executable name: MicrosoftEdgeCP.exe