With a SSL VPN client with MFA enabled, the login form needs to display either another text box to insert the MFA code or a message stating that a MFA code needs to be appended to the password.
The current login form is rather crude and causes a lot of helpdesk calls because they don't realize ( or keep forgetting) that their MFA code needs to be inserted after their password.
An upgraded form with logo that looks more professional would be my preference please.

As the Title, Clients with the gateway on CoreSW can not use Heartbeat to the Internal Firewall XG because the Heartbeat packet is route by the External Firewall XG.

When the option "Use web authentication for unknown users" is selected in the Firewall Rules, the Policy Tester shows the result as "Allowed" even for unauthenticated users. I suggest it should display as Blocked for unauthenticated users.

I suggest the implementation of network map visualization to watch os type, hostname, IP, open ports and manage their network access.

Any interface configured as WAN cannot have their's ISP's internal DNS server configured right on the interface, just have to use those 3 DNS servers on the DNS page. Adding this function will allow many ISP DNS Servers to respond faster for any resolution, increasing the response time for the request for that ISP that runs better than with public DNS Servers, and making the end-users more unsatisfied with the WAN performance.

Just adding the option to set DNS Servers on the interface configuration for each WAN will resolve this issue.

It would be really useful if you could apply QoS and routing policy to data generated by the XG, such as signature updates. So these updates do not impact the WAN bandwidth low speed links.

We have a number of XG firewalls connected to very low bandwidth / high latency WAN connections.

On the old Cyberoam OS it was possible to select which pattern modules are updated automatically. This saved unnecessary data being downloaded as we only need IPS and Application signatures to stay up to date.

Allow Link-local IP for Health check under gateways. AWS uses link-local IPs for interface IP so if you are using tunnel interface mode for ipsec and have both gateways setup for failover you are unable to use a health check currently because you do not allow link-local IP. You are able to ping it though device console so it would work if you would just allow Link local IPs

please add an option for easy Routing information to choose between only ipv4 or ipv6 for networks which have both and uses DDNS

We have users who are connecting via PPTP to the VPN that are not terminating their PPTP VPN session on their PCs. They are using Windows Built-In VPN application to connect.

This results in a single user having several sessions taking up IP address from our set VPN IP range.

Unless I'm not seeing it, can the option to terminate PPTP VPN sessions based on activity be added?

We're using SG330 (SFOS 18.0.4 MR-4)

Cisco ASA to Sophos XG Migration tool

Currently WAF rules can only have their source filtered by IP or by Network, while regular DNAT rules can be filtered by IP, IP Range, IP List, MAC Address, MAC List, Host Group, Network, FQDN Host, FQDN Host Group, or Country Group.

I'd like the functionality of the WAF source filter to be expanded to have the same capabilities as a full DNAT rule.

I'm specifically after the FQDN host so we can filter and use DynDNS hostnames but the other things would be handy as welll

DCs can only authenticate against one UPN domain. My AD uses several UPN domains, so that e-mails coincide with user accounts, as we own different domains. So I can only use Heartbeat authenticacion with users in the same domain as configured in DC, or I have to create as many DCs as domains, which does not make any sense.

Can you enable the capability to authenticate against different domains, by allowing to add several domains in the domain field of the DC access server?

as described in your article: https://docs.sophos.com/nsg/sophos-firewall/17.5/Help/en-us/webhelp/onlinehelp/nsg/sfos/tasks/MicrosoftRemoteDesktopGateway2008andR2.html
As soon as a new HTTP based rule configuration has been created and saved or an existing HTTP based rule configuration has been altered and saved, all HTTP based business rules will be restarted. Any underlying client connection using a HTTP based business rule will get lost and has to be re-established.

This should not happen, and it should be corrected.

Want to get the following details for VPN users.

1. User create date


2. User last modified date


3. User last connection date


4. User last date of password change

This information via API would assist with internal compliance audit and auto disable of accounts not in use as well as automated emails to change passwords.

Bandwidth graph for IPSEC VPN tunnel gives us the overview of the traffic consume by the VPN tunnel currently which is not possible in Sophos XG, only the interface graphs can be view.

In v18 of SFOS of my XG firewall, SSL/TLS inspection is a global on/off setting. I would like to be able to control the use of SSL/TLS inspection per rule instead of globally.

I have an old copier trying to send secure emails and the inspection engine is erroring out with a timeout error. There is no way to make an exception for this. If could just create a new firewall rule so this copier could send out emails would be great while leaving SSL/TLS inspection enabled for all the other rules. v17 everything worked fine.

Sender field, in quarantine report email, currently presents only the forged/fake address of a Phishing/Spoofing email.

A good idea would be to add the real Sender Address, and maybe color it with RED to be eye-catchy and alert the user to pay attention to it.
Alternatively, display only the original email address.

Actually, when phase 1 expires with IKEv2 and RSA-Keys, reauthenticating happens, which is leading to a short VPN interruption ans the corresponding log entries showing the connection as down and up again.
I'd like to propose to implement "reauth=no" in the VPN Configuration. This will lead to rekeying instead of reauthentication when phase 1 expires. Rekeying happens on the fly without interrupting the tunnel and also without the log entries.
This feature request was created based on the Sophos support ticket number [ ref:00D301GN6a.5003Z1728jB:ref ].