Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos Firewall: v20.0 GA: Feedback and experiences

Release Post:  Sophos Firewall v20 is Now Available  

The EAP Post:  Sophos Firewall: v20.0 EAP1: Feedback and experiences  

The old V19.5 MR3 Post:  Sophos Firewall: v19.5 MR3: Feedback and experiences  

To make the tracking of issues / feedback easier: Please post a potential Sophos Support Case ID within your initial post, so we can track your feedback/issue. 

Release Notes:  https://docs.sophos.com/releasenotes/output/en-us/nsg/sf_200_rn.html 



This thread was automatically locked due to age.
Parents
  • Version 20 has a default allow firewall rule that allows all traffic even before filtering rules are set up.

    Why?

    Why would a firewall whose sole purpose is to protect a network from botnet/command and control activity, unauthorized application/web usage allow all outgoing activity on first install?

    Version 19 had no such default allow rule, and the firewall administrator had to create an outgoing rule after configuring application/IPS/web filtering, ect.

    Also the default TLS inspection rule stays on top of all other user-created rules, and allows "maximum compatibility". Why is it so many sites do not function when the TLS inspection rules are set to "block insecure SSL"? I have noticed that many banking/financial institutions do not function when block insecure SSL rules are used. Is there some deeper part to the story here about why secure SSL seems to be so hard to implement???

  • Do you mean during a restart or at first installation. I have noticed in past versions that some of my devices access the internet after an XG restart until the configuration is fully loaded. WAN access should be disabled after restart until the configuration is loaded.

    I disabled the default SSL/TLS rule and cloned it so I could move it around the SSL/TLS processing order. The exception list is very  long and makes you winder why you even try to use it and doesn't inspect UDP traffic yet?

    Ian

    XG115W - v20.0.2 MR-2 - Home

    XG on VM 8 - v21 GA

    If a post solves your question please use the 'Verify Answer' button.

  • SSL is TCP anyway, and it's good to block UDP on port 443 (QUIC)

  • It does not block it, it allows UDP through unchecked. Recently FB appears to have started using QUIC for the application.

    Ian

    XG115W - v20.0.2 MR-2 - Home

    XG on VM 8 - v21 GA

    If a post solves your question please use the 'Verify Answer' button.

  • Instead of clicking "Block QUIC" in the firewall rule, If you create a firewall rule at the top to block incoming/outgoing UDP on port 443, you mean it does not block it?

Reply Children
No Data