We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information

Accept

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)

CloudGen Firewall

NextGen Firewall X

Network Access Client

Web Security Gateway

Web Security Service

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

Email Security Gateway

Forensics & Incident Response

Message Archiver

Cloud Archiving Service

Cloud-to-Cloud Backup

Intronis Backup

Reference / FAQ

TechSummit 2018

Barracuda Web Security Gateway

Overview Documentation Training Certification Materials

CloudGen Firewall

NextGen Firewall X

Network Access Client

Web Security Gateway

Web Security Service

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

Email Security Gateway

Forensics & Incident Response

Message Archiver

Cloud Archiving Service

Cloud-to-Cloud Backup

Intronis Backup

Reference / FAQ

TechSummit 2018

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