topic Re: Chromium Edge object in App Control/URL Filtering in Firewall and Security Management

Chromium Edge object in App Control/URL Filtering

Alex- — Sun, 16 Mar 2025 19:04:07 GMT

R1.20 T98

A customer has a strict APPI/URLF policy and wanted to go further by only allowing MS Edge (Chromium engineering) using the relevant object in the policy.

While I don't have the exact details, it worked as intended.

Fast forward to now, the customer had to remove that object as it was effectively allowing everything. That probably because of the broad category it's sitting in.

For a while we tried that object to allow Edge updates but even than it acted more like a catch-all for ay kind of traffic.

Two questions:

a) What is the Chromium Edge object supposed to cover?

b) Is there a way to use it in the policy to allow Edge as web agent?

An SR is open for clarification.

Re: Chromium Edge object in App Control/URL Filtering

the_rock — Sun, 16 Mar 2025 20:25:59 GMT

Let us know what TAC says.

Andy

Re: Chromium Edge object in App Control/URL Filtering

Alex- — Wed, 26 Mar 2025 05:32:17 GMT

In the end, the customer didn't have the time to dig into this so the TAC case was closed, but as far as we could see the Edge Chromium object allowed everything, even beyond Microsoft services, and they have full hTTPS Inspection.

To be continued. 😀

Re: Chromium Edge object in App Control/URL Filtering

PhoneBoy — Wed, 26 Mar 2025 13:38:51 GMT

I know you can use the Application Control Signature Tool to create a signature for specific User Agent strings, which is what I assume our native signature for EDGE should be doing.
TAC would be needed to figure out if the built-in signature is actually working correctly or not.