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???

  • Can you explain - what your concerns are here? 
    So if you are setting up the firewall, in a "pre registrations state" the firewall allows everything to the internet. That is to allow an administrator to setup the firewall and still have access to tools like a password safe etc. But this state should not be the usual case of a firewall. 

    And there should be no difference between V20 and V19.5. It has the same behavior pre registration. 

    The Default TLS inspection rule is setup to "No do anything" for the domains, you add to the list and are added by Sophos to the list. If you do not create a own list, it will not do anything. 

    About TLS Inspection: There are two different modules working here: 1. Inspection by decryption & 2. blocking of ciphers / methods you dont want to have. They can work independently. So you can block for example RC4 but not decrypt the traffic. 

    And if you find a website not working with blocking of insecure cipher, you can build an exclusion. But that is nothing, SFOS "related". 

    __________________________________________________________________________________________________________________

Reply
  • Can you explain - what your concerns are here? 
    So if you are setting up the firewall, in a "pre registrations state" the firewall allows everything to the internet. That is to allow an administrator to setup the firewall and still have access to tools like a password safe etc. But this state should not be the usual case of a firewall. 

    And there should be no difference between V20 and V19.5. It has the same behavior pre registration. 

    The Default TLS inspection rule is setup to "No do anything" for the domains, you add to the list and are added by Sophos to the list. If you do not create a own list, it will not do anything. 

    About TLS Inspection: There are two different modules working here: 1. Inspection by decryption & 2. blocking of ciphers / methods you dont want to have. They can work independently. So you can block for example RC4 but not decrypt the traffic. 

    And if you find a website not working with blocking of insecure cipher, you can build an exclusion. But that is nothing, SFOS "related". 

    __________________________________________________________________________________________________________________

Children
  • Interesting, but strange answer.

    A post from another forum I visit advises that ASUS router/firewall and PFSense also have the same startup issue with open internet access for a few seconds.

    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.