Forum Discussion
Microsoft Defender for Endpoint Web Filtering Problem
HI All, i have a strange issue with Microsoft Defender for Endpoint, network protection is in block mode, i add custom indicator, and web page is blocked by Microsoft Edge but not in other Browser Like Chrome, Opera or Firefox, in the past websites ar correctly blocked, there are other person with this issue ?
Many Thanks,
Regards,
Guido
Deleted per the documentation
Known issues and limitations
Network protection does not currently support SSL inspection, which might result in some sites being allowed by web content filtering that would normally be blocked. Sites would be allowed due to a lack of visibility into encrypted traffic after the TLS handshake has taken place and an inability to parse certain redirects. This includes redirections from some web-based mail login pages to the mailbox page. As an accepted workaround, you can create a custom block indicator for the login page to ensure no users are able to access the site. Keep in mind, this might block their access to other services associated with the same website.
- it's a known issue and we are waiting for any updates from MS, content filtering is working with Edge but not with chrome and Firefox.
- If you read the MS docs you will find that it is unable to filter HTTPS traffic on third party browsers. The only real options to all such filtering is block third party browsers and only use Edge.
RobertCrane hi Robert,
Thanks so mouch for your respons, but in the documentation i See that web content filtering support other browser https://learn.microsoft.com/en-us/microsoft-365/security/defender-endpoint/web-content-filtering?view=o365-worldwide
with network protection in block mode, infact a few months later this option works without problem, in the ticket Ms confirm that webcontentfiltering must work,
Many Thanks
regards
guido
Deleted per the documentation
Known issues and limitations
Network protection does not currently support SSL inspection, which might result in some sites being allowed by web content filtering that would normally be blocked. Sites would be allowed due to a lack of visibility into encrypted traffic after the TLS handshake has taken place and an inability to parse certain redirects. This includes redirections from some web-based mail login pages to the mailbox page. As an accepted workaround, you can create a custom block indicator for the login page to ensure no users are able to access the site. Keep in mind, this might block their access to other services associated with the same website.
- The issue is likely due to browser-specific settings or differences in how browsers handle security policies. Microsoft Edge may be properly enforcing network protection policies, while other browsers like Chrome, Opera, or Firefox might not be fully integrated or configured to respect those policies. Check if browser extensions or additional configurations are needed to enforce network protection across all browsers.
Hello question92120 , not is not a problem of Browser in the period where i have a problem, is a known problem, now all works fine with all Browser.
Many Thanks for your reposnse,
Regards,
Guido
